# Built in plugins moved to their own repos **URL:** \ **Category:** Elasticsearch\ **Created:** [December 5, 2011, 7:02pm UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070 "2011-12-05T19:02:52Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [December 5, 2011, 7:02pm UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070/1 "2011-12-05T19:02:52Z")
Heya, The built in plugins that existed in the elasticsearch/elasticsearch repo have now moved to their own repos. The installation command to install them have changed, and their versions work well with 0.18.5 (and obviously, 0.19). More info here: [https://github.com/elasticsearch/elasticsearch/issues/1520](https://github.com/elasticsearch/elasticsearch/issues/1520). The plugins have maven as the build system, which I hope will simplify things by acting as samples for custom plugins and easily "import" them into the IDE. Now that effectively, we can have elasticsearch as a single module, I will try and see how hard it is to move from gradle to maven on elasticsearch itself as well. Will update... -shay.banon ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [December 5, 2011, 7:29pm UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070/2 "2011-12-05T19:29:13Z")
> Now that effectively, we can have elasticsearch as a single module, > I will try and see how hard it is to move from gradle to maven on > elasticsearch itself as well. Will update... Not a Java person, but my experience with compiling ES via gradle was a joy, and my very limited experience with maven has been a good deal more painful clint ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [December 5, 2011, 7:35pm UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070/3 "2011-12-05T19:35:15Z")
Agreed, its simpler, but harder on getting up and running in developing elasticsearch (especially with problematic recent changes in gradle). It will be as simpel as (which is how the plugins work now): 1. install maven (apt-get maven, brew install maven) (once) 2. run "mvn assembly:assembly -DskipTests" and you will have the distribution under target. The good thing with maven is that you simply import it into the IDE (all support maven nicely) and on you go with developing elasticsearch. -shay.banon On Mon, Dec 5, 2011 at 9:29 PM, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)wrote: > > Now that effectively, we can have elasticsearch as a single module, > > I will try and see how hard it is to move from gradle to maven on > > elasticsearch itself as well. Will update... > > Not a Java person, but my experience with compiling ES via gradle was a > joy, and my very limited experience with maven has been a good deal more > painful > > clint ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 5, 2011, 7:39pm UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070/4 "2011-12-05T19:39:38Z")
100% agree, Shay. Is there any way we can help you to "mavenize" Elasticsearch ? David 😉 @dadoonet Le 5 déc. 2011 à 20:35, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit : > Agreed, its simpler, but harder on getting up and running in developing elasticsearch (especially with problematic recent changes in gradle). It will be as simpel as (which is how the plugins work now): > > 1. install maven (apt-get maven, brew install maven) (once) > 2. run "mvn assembly:assembly -DskipTests" and you will have the distribution under target. > > The good thing with maven is that you simply import it into the IDE (all support maven nicely) and on you go with developing elasticsearch. > > -shay.banon > > On Mon, Dec 5, 2011 at 9:29 PM, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com) wrote: > > > Now that effectively, we can have elasticsearch as a single module, > > I will try and see how hard it is to move from gradle to maven on > > elasticsearch itself as well. Will update... > > Not a Java person, but my experience with compiling ES via gradle was a > joy, and my very limited experience with maven has been a good deal more > painful > > clint ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [December 5, 2011, 8:10pm UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070/5 "2011-12-05T20:10:56Z")
i will give it a quick go in the next couple of days, and will probably leave things to do later (like porting the debian packaging to maven) that I could definitely use help with... On Mon, Dec 5, 2011 at 9:39 PM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote: > 100% agree, Shay. > Is there any way we can help you to "mavenize" Elasticsearch ? > > David 😉 > @dadoonet > > Le 5 déc. 2011 à 20:35, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit : > > Agreed, its simpler, but harder on getting up and running in developing > elasticsearch (especially with problematic recent changes in gradle). It > will be as simpel as (which is how the plugins work now): > > 1. install maven (apt-get maven, brew install maven) (once) > 2. run "mvn assembly:assembly -DskipTests" and you will have the > distribution under target. > > The good thing with maven is that you simply import it into the IDE (all > support maven nicely) and on you go with developing elasticsearch. > > -shay.banon > > On Mon, Dec 5, 2011 at 9:29 PM, Clinton Gormley \< [clint@traveljury.com](mailto:clint@traveljury.com) > [clint@traveljury.com](mailto:clint@traveljury.com)\> wrote: > > > > Now that effectively, we can have elasticsearch as a single module, > > > I will try and see how hard it is to move from gradle to maven on > > > elasticsearch itself as well. Will update... > > > > Not a Java person, but my experience with compiling ES via gradle was a > > joy, and my very limited experience with maven has been a good deal more > > painful > > > > clint ---
**Author:** ![Loco\_Jay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/loco_jay/32/2982_2.png) [@Loco\_Jay](https://discuss.elastic.co/u/Loco_Jay)\ **Post date:** [December 7, 2011, 4:59pm UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070/6 "2011-12-07T16:59:25Z")
would be great to reference them back as git submodules so one can see any changes in one place. On Dec 5, 2011, at 2:29 PM, Clinton Gormley wrote: > > Now that effectively, we can have elasticsearch as a single module, > > I will try and see how hard it is to move from gradle to maven on > > elasticsearch itself as well. Will update... > > Not a Java person, but my experience with compiling ES via gradle was a > joy, and my very limited experience with maven has been a good deal more > painful > > clint ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [December 7, 2011, 5:33pm UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070/7 "2011-12-07T17:33:37Z")
I think that separating the plugins is a great idea. Good job! I have built plugins using both Maven and SBT (Scala Build Tool). The only trick is conforming to the elasticsearch plugin naming convention/packaging especially since Maven is about convention over configuration. Ivan On Wed, Dec 7, 2011 at 8:59 AM, Loco Jay [locojaydev@gmail.com](mailto:locojaydev@gmail.com) wrote: > would be great to reference them back as git submodules so one can see any changes in one place. > > On Dec 5, 2011, at 2:29 PM, Clinton Gormley wrote: > > > > Now that effectively, we can have elasticsearch as a single module, > > > I will try and see how hard it is to move from gradle to maven on > > > elasticsearch itself as well. Will update... > > > > Not a Java person, but my experience with compiling ES via gradle was a > > joy, and my very limited experience with maven has been a good deal more > > painful > > > > clint ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:46am UTC](https://discuss.elastic.co/t/built-in-plugins-moved-to-their-own-repos/6070/8 "2017-07-06T03:46:08Z")