I agree, but for people who use Ivy (and build systems that use Ivy
internally), they will run into problems with source/javadoc separate jar
files (it does not support that...). Updating the IDE to point to the source
one is quite simple.
As you can tell, I am not a big fan of maven. But, I am willing to go the
extra mile to support it, but just that mile :). I am working most of today
at getting things up into the OSS sonatype thingy, time that I am waisting
in not developing elasticsearch. This is what I almost always found with
maven, the time you spend on it just does not justifies it.
On Fri, Apr 2, 2010 at 8:49 PM, Paolo Castagna <
Shay Banon wrote:
Don't think I am going to do that for maven... . The jar file itself will
also hold the code, source (and javadoc).
This will probably cause problems to people wanting to use plugins
And everybody else who rely on the "conventions" in place:
"If you browse the Maven central repository, you will notice
that the classifiers sources and javadoc are used to deploy
the project source code and API docs along with the packaged