Issue 90: Upload version 2.3 to the Maven repository.
Status:  WontFix
Owner:
extremec...@gmail.com
Closed:  May 2008
Reported by extremec...@gmail.com, Mar 13, 2008
Need to upload the latest version.
 
Mar 15, 2008
#1 extremec...@gmail.com

I added the request to the Maven folks. You can track the progress through their
upload process here:

http://jira.codehaus.org/browse/MAVENUPLOAD-1965


Status: Started
Mar 31, 2008
#2 calm...@gmail.com
Please update the pom.xml with the necessary information to declare the runtime only
dependencies correctly. It's just a few lines of xml. I guess this issue won't be
completed otherwise. 

I also suggest to set the version tag in the pom.xml to the correct version while at
it. Now it says 2.2.1. 

I'm thinking of trying out the jmesa project but won't consider it useful until Maven
upload is done.
Mar 31, 2008
#3 extremec...@gmail.com
I have the version updated on the trunk. The build I did for the Maven folks uses the
pom.xml from the trunk so it is right. I'm not sure how to declare runtime
dependencies. I do not use Maven myself so I depend on the community to keep that
pom.xml updated.

I do find it odd that you would discount a project because it is not in the Maven
upload site.

One developer sent me a link on how to set up the subversion repository as my own
Maven repository for this one file. I plan on doing that in the upcoming weeks.

May 23, 2008
#4 extremec...@gmail.com
For now I have to delay trying to upload to Maven. If someone would like to pick up
the job that would be greatly appreciated.
Status: WontFix
Jun 5, 2009
#5 Mitch.Wa...@gmail.com
I know that this is closed, however I wanted to respond to your earlier comment about
not understanding the discounting of a project lacking maven support. I personally
like the look of the project and would be interested in trying it out in my own
projects, but I won't tie my maven-built project to a dependency that you would need
to go download manually. You yourself have said (in other comments that I have read
for other issues) that you would like your own project to be something that someone
could easily check out and use with minimal effort. Maven users want the same thing,
which is why we use the tool. But that ease-of-use grinds to a halt if you can't get
the dependencies out of a maven repo, or you find the only version in a repo woefully
out of date and have to download it and manually install it in your local repo. At
this point I can get any major dependency I want from a maven repository that I want,
without manually locating the project and pulling it down to my local box. 

As a user, I want to check out just the source of a project (and not some lib
directory) and set it up to run in my IDE or build it with a few quick commands. I
don't need separate copies of dependencies on my hard disk for *every* project I
download. I don't want to guess what version the commons-lang.jar (or insert a
commonly used dependency here) that came in a project is.

Hopefully that gave some insight as to *why* someone would feel that way, and I'm
sorry if that turned into a rant.