Following the extraction of the plugins into their own repos, the main repo
(elasticsearch) moved to maven for the build system (single module, so its
almost bearable). More details in the issue: https://github.com/elasticsearch/elasticsearch/issues/1523.
Hopefully, this will make things simpler for people to start "develop" on
elasticsearch, which was one of the triggers. Another one was recent
changes in gradle that made it less useful (at least in my eyes). And
finally, the fact that we can have a single module project (donno, maybe
maven is better now, but previously, it was horrible when trying to use it
in multi module projects, but in any case, keep it simple...).
Hopefully, this will make things simpler for people to start "develop" on
elasticsearch, which was one of the triggers. Another one was recent
changes in gradle that made it less useful (at least in my eyes). And
finally, the fact that we can have a single module project (donno, maybe
maven is better now, but previously, it was horrible when trying to use it
in multi module projects, but in any case, keep it simple...).
The main problem was the new dependency resolution. With how it worked,
there was an IntelliJ file already configured to point to the relevant
dependencies downloaded by gradle, but with the new one, the location is
generated and is not constant. There were ways around it, but that was what
flipped things over and caused moving to maven, where I hope getting
starting with developing elasticsearch is now much simpler. Also, since now
its a single module project (I had many problems with multi module projects
in maven) because we moved the plugins to their own repos/projects, I knew
that it won't be that bad (maven).
Hopefully, this will make things simpler for people to start "develop" on
elasticsearch, which was one of the triggers. Another one was recent
changes in gradle that made it less useful (at least in my eyes). And
finally, the fact that we can have a single module project (donno, maybe
maven is better now, but previously, it was horrible when trying to use
it
in multi module projects, but in any case, keep it simple...).
But where are the plugins? Moving them to their own SCM repository is a
nice change, but they still have to be uploaded to a Maven repository in
order for developers using Maven and resolving ES dependencies using Maven
to be able to use them. The bin/install approach only works for
command-line usage of ES. At the moment, I have to upload the cloud plugin
(for example) to my own Maven repository. ugh.
-- jim
On Tuesday, December 6, 2011 9:08:23 AM UTC-5, kimchy wrote:
Hopefully, this will make things simpler for people to start "develop" on
elasticsearch, which was one of the triggers. Another one was recent
changes in gradle that made it less useful (at least in my eyes). And
finally, the fact that we can have a single module project (donno, maybe
maven is better now, but previously, it was horrible when trying to use it
in multi module projects, but in any case, keep it simple...).
Le 14 mai 2012 à 21:19, James Cook jcook@pykl.com a écrit :
But where are the plugins? Moving them to their own SCM repository is a nice change, but they still have to be uploaded to a Maven repository in order for developers using Maven and resolving ES dependencies using Maven to be able to use them. The bin/install approach only works for command-line usage of ES. At the moment, I have to upload the cloud plugin (for example) to my own Maven repository. ugh.
-- jim
On Tuesday, December 6, 2011 9:08:23 AM UTC-5, kimchy wrote:
Following the extraction of the plugins into their own repos, the main repo (elasticsearch) moved to maven for the build system (single module, so its almost bearable). More details in the issue: Move project build to maven · Issue #1523 · elastic/elasticsearch · GitHub.
Hopefully, this will make things simpler for people to start "develop" on elasticsearch, which was one of the triggers. Another one was recent changes in gradle that made it less useful (at least in my eyes). And finally, the fact that we can have a single module project (donno, maybe maven is better now, but previously, it was horrible when trying to use it in multi module projects, but in any case, keep it simple...).
Sorry, I see that the plugins are in Maven, but they have a new version
number independent of ES. Thanks.
On Monday, May 14, 2012 3:19:25 PM UTC-4, James Cook wrote:
But where are the plugins? Moving them to their own SCM repository is a
nice change, but they still have to be uploaded to a Maven repository in
order for developers using Maven and resolving ES dependencies using Maven
to be able to use them. The bin/install approach only works for
command-line usage of ES. At the moment, I have to upload the cloud plugin
(for example) to my own Maven repository. ugh.
-- jim
On Tuesday, December 6, 2011 9:08:23 AM UTC-5, kimchy wrote:
Hopefully, this will make things simpler for people to start "develop" on
elasticsearch, which was one of the triggers. Another one was recent
changes in gradle that made it less useful (at least in my eyes). And
finally, the fact that we can have a single module project (donno, maybe
maven is better now, but previously, it was horrible when trying to use it
in multi module projects, but in any case, keep it simple...).
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.