# Contributing a JMS River Plugin

**URL:** <https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730>\
**Category:** Elasticsearch\
**Created:** [April 29, 2013, 1:44pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730 "2013-04-29T13:44:16Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aall\_Spemmer](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Aall\_Spemmer](https://discuss.elastic.co/u/Aall_Spemmer)\
**Post date:** [April 29, 2013, 1:44pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/1 "2013-04-29T13:44:16Z")

</div>

How would I go about submitting the code for a JMS river plugin I created?  
It didn't seem like I should go through the whole fork, clone, pull request  
thing, as I am not actually modifying the elasticsearch code.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [April 29, 2013, 2:27pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/2 "2013-04-29T14:27:47Z")

</div>

You can add your project to the list of contributed third-party code. Fork  
the documentation repo and add it to the client page.

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

[https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile](https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile)

--  
Ivan

On Mon, Apr 29, 2013 at 6:44 AM, Aall Spemmer [sssml2011@gmail.com](mailto:sssml2011@gmail.com) wrote:

> How would I go about submitting the code for a JMS river plugin I  
> created? It didn't seem like I should go through the whole fork, clone,  
> pull request thing, as I am not actually modifying the elasticsearch code.
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Aall\_Spemmer](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Aall\_Spemmer](https://discuss.elastic.co/u/Aall_Spemmer)\
**Post date:** [April 29, 2013, 2:43pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/3 "2013-04-29T14:43:07Z")

</div>

Thanks. There don't appear to be any other river plugins listed here.  
Wouldn't [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/river/) be better a  
place?

On Monday, April 29, 2013 10:27:47 AM UTC-4, Ivan Brusic wrote:

> You can add your project to the list of contributed third-party code. Fork  
> the documentation repo and add it to the client page.
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/clients/)
> 
> [https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile](https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile)
> 
> --  
> Ivan
> 
> On Mon, Apr 29, 2013 at 6:44 AM, Aall Spemmer \<[sssm...@gmail.com](mailto:sssm...@gmail.com)\<javascript:\>
> 
> > wrote:
> 
> > How would I go about submitting the code for a JMS river plugin I  
> > created? It didn't seem like I should go through the whole fork, clone,  
> > pull request thing, as I am not actually modifying the elasticsearch code.
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [April 29, 2013, 2:45pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/4 "2013-04-29T14:45:30Z")

</div>

Hey,

the rivers are listed under plugins at the moment

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

if you feel, your river is ready for production, drop us a note and are  
happy to put it on the homepage.

--Alex

On Mon, Apr 29, 2013 at 4:43 PM, Aall Spemmer [sssml2011@gmail.com](mailto:sssml2011@gmail.com) wrote:

> Thanks. There don't appear to be any other river plugins listed here.  
> Wouldn't [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/river/) be better a  
> place?
> 
> On Monday, April 29, 2013 10:27:47 AM UTC-4, Ivan Brusic wrote:
> 
> > You can add your project to the list of contributed third-party code.  
> > Fork the documentation repo and add it to the client page.
> > 
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/**guide/clients/)[http://www.elasticsearch.org/guide/clients/](http://www.elasticsearch.org/guide/clients/)  
> > [https://github.com/\*\*elasticsearch/elasticsearch.](https://github.com/**elasticsearch/elasticsearch.)\*\*  
> > [github.com/blob/master/guide/\*\*clients/index.textile](http://github.com/blob/master/guide/**clients/index.textile)[https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile](https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile)
> > 
> > --  
> > Ivan
> > 
> > On Mon, Apr 29, 2013 at 6:44 AM, Aall Spemmer [sssm...@gmail.com](mailto:sssm...@gmail.com) wrote:
> > 
> > > How would I go about submitting the code for a JMS river plugin I  
> > > created? It didn't seem like I should go through the whole fork, clone,  
> > > pull request thing, as I am not actually modifying the elasticsearch code.
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google  
> > > Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send  
> > > an email to elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com).
> > > 
> > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out)  
> > > .
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [April 29, 2013, 6:19pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/5 "2013-04-29T18:19:36Z")

</div>

Thanks for correcting my mistake Alexander. Wrong page. It does show the  
need to re-organize the docs though. 🙂 Thinking in terms of "modules",  
which is primarily a code-level concept, can be confusing.

--  
Ivan

On Mon, Apr 29, 2013 at 7:45 AM, Alexander Reelsen [alr@spinscale.de](mailto:alr@spinscale.de) wrote:

> Hey,
> 
> the rivers are listed under plugins at the moment  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/modules/plugins/)
> 
> if you feel, your river is ready for production, drop us a note and are  
> happy to put it on the homepage.
> 
> --Alex
> 
> On Mon, Apr 29, 2013 at 4:43 PM, Aall Spemmer [sssml2011@gmail.com](mailto:sssml2011@gmail.com) wrote:
> 
> > Thanks. There don't appear to be any other river plugins listed here.  
> > Wouldn't [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/river/) be better a  
> > place?
> > 
> > On Monday, April 29, 2013 10:27:47 AM UTC-4, Ivan Brusic wrote:
> > 
> > > You can add your project to the list of contributed third-party code.  
> > > Fork the documentation repo and add it to the client page.
> > > 
> > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/**guide/clients/)[http://www.elasticsearch.org/guide/clients/](http://www.elasticsearch.org/guide/clients/)  
> > > [https://github.com/\*\*elasticsearch/elasticsearch.](https://github.com/**elasticsearch/elasticsearch.)\*\*  
> > > [github.com/blob/master/guide/\*\*clients/index.textile](http://github.com/blob/master/guide/**clients/index.textile)[https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile](https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile)
> > > 
> > > --  
> > > Ivan
> > > 
> > > On Mon, Apr 29, 2013 at 6:44 AM, Aall Spemmer [sssm...@gmail.com](mailto:sssm...@gmail.com) wrote:
> > > 
> > > > How would I go about submitting the code for a JMS river plugin I  
> > > > created? It didn't seem like I should go through the whole fork, clone,  
> > > > pull request thing, as I am not actually modifying the elasticsearch code.
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to the Google  
> > > > Groups "elasticsearch" group.  
> > > > To unsubscribe from this group and stop receiving emails from it, send  
> > > > an email to elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com).
> > > > 
> > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out)  
> > > > .
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google Groups  
> > > "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send an  
> > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Aall\_Spemmer](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Aall\_Spemmer](https://discuss.elastic.co/u/Aall_Spemmer)\
**Post date:** [May 2, 2013, 11:17pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/6 "2013-05-02T23:17:14Z")

</div>

My JMS river is ready for production. Please add a link to  
[GitHub - qotho/elasticsearch-river-jms: Java Messaging Service (JMS) River Plugin for ElasticSearch](https://github.com/qotho/elasticsearch-river-jms) on the elasticsearch home  
page. Thanks.

I have also submitted a pull request to add a link to the  
guide/reference/modules/plugins section of the documentation.

On Monday, April 29, 2013 10:45:30 AM UTC-4, Alexander Reelsen wrote:

> Hey,
> 
> the rivers are listed under plugins at the moment  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/modules/plugins/)
> 
> if you feel, your river is ready for production, drop us a note and are  
> happy to put it on the homepage.
> 
> --Alex
> 
> On Mon, Apr 29, 2013 at 4:43 PM, Aall Spemmer \<[sssm...@gmail.com](mailto:sssm...@gmail.com)\<javascript:\>
> 
> > wrote:
> 
> > Thanks. There don't appear to be any other river plugins listed here.  
> > Wouldn't [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/river/) be better a  
> > place?
> > 
> > On Monday, April 29, 2013 10:27:47 AM UTC-4, Ivan Brusic wrote:
> > 
> > > You can add your project to the list of contributed third-party code.  
> > > Fork the documentation repo and add it to the client page.
> > > 
> > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/**guide/clients/)[http://www.elasticsearch.org/guide/clients/](http://www.elasticsearch.org/guide/clients/)  
> > > [https://github.com/\*\*elasticsearch/elasticsearch.](https://github.com/**elasticsearch/elasticsearch.)\*\*  
> > > [github.com/blob/master/guide/\*\*clients/index.textile](http://github.com/blob/master/guide/**clients/index.textile)[https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile](https://github.com/elasticsearch/elasticsearch.github.com/blob/master/guide/clients/index.textile)
> > > 
> > > --  
> > > Ivan
> > > 
> > > On Mon, Apr 29, 2013 at 6:44 AM, Aall Spemmer [sssm...@gmail.com](mailto:sssm...@gmail.com) wrote:
> > > 
> > > > How would I go about submitting the code for a JMS river plugin I  
> > > > created? It didn't seem like I should go through the whole fork, clone,  
> > > > pull request thing, as I am not actually modifying the elasticsearch code.
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to the Google  
> > > > Groups "elasticsearch" group.  
> > > > To unsubscribe from this group and stop receiving emails from it, send  
> > > > an email to elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com).
> > > > 
> > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out)  
> > > > .
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google Groups  
> > > "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send an  
> > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Aall\_Spemmer](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Aall\_Spemmer](https://discuss.elastic.co/u/Aall_Spemmer)\
**Post date:** [May 2, 2013, 11:18pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/7 "2013-05-02T23:18:05Z")

</div>

My JMS river is ready for production. Please add a link to  
[https://github.com/qotho/elasticsearch-river-jms](https://github.com/qotho/elasticsearch-river-jms) on the elasticsearch home  
page. Thanks.

I have also submitted a pull request to add a link to the  
guide/reference/modules/plugins section of the documentation.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Roy\_Russo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roy_russo/32/44835_2.png) [@Roy\_Russo](https://discuss.elastic.co/u/Roy_Russo)\
**Post date:** [May 3, 2013, 1:52am UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/8 "2013-05-03T01:52:56Z")

</div>

> My JMS river is ready for production.

You may want to change this on your README then: "NOTE: DOESN'T WORK YET"

😉

On Thursday, May 2, 2013 7:18:05 PM UTC-4, Aall Spemmer wrote:

> My JMS river is ready for production. Please add a link to  
> [GitHub - qotho/elasticsearch-river-jms: Java Messaging Service (JMS) River Plugin for ElasticSearch](https://github.com/qotho/elasticsearch-river-jms) on the elasticsearch  
> home page. Thanks.
> 
> I have also submitted a pull request to add a link to the  
> guide/reference/modules/plugins section of the documentation.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Aall\_Spemmer](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Aall\_Spemmer](https://discuss.elastic.co/u/Aall_Spemmer)\
**Post date:** [May 3, 2013, 10:19am UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/9 "2013-05-03T10:19:32Z")

</div>

Sorry, I thought it was clear that refers to installing the plugin using  
the elasticsearch plugin script. I haven't gotten this to work yet, other  
than running Maven to create the ZIP and using the "file://" URL method to  
install the ZIP locally.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [May 3, 2013, 1:52pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/10 "2013-05-03T13:52:56Z")

</div>

Non-explicit (no url scheme) remote plugin installs will not work unless it  
is an official Elasticsearch plugin or a [Maven.org/Sonatype](http://Maven.org/Sonatype) project. You  
can upload the jar somewhere and use a full URL path for the install. For  
example, Jorg's JDBC river plugin: plugin -url [http://bit.ly/Yp2Drj](http://bit.ly/Yp2Drj) -install  
river-jdbc

--  
Ivan

On Fri, May 3, 2013 at 3:19 AM, Aall Spemmer [sssml2011@gmail.com](mailto:sssml2011@gmail.com) wrote:

> Sorry, I thought it was clear that refers to installing the plugin using  
> the elasticsearch plugin script. I haven't gotten this to work yet, other  
> than running Maven to create the ZIP and using the "file://" URL method to  
> install the ZIP locally.
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Aall\_Spemmer](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Aall\_Spemmer](https://discuss.elastic.co/u/Aall_Spemmer)\
**Post date:** [May 3, 2013, 4:02pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/11 "2013-05-03T16:02:07Z")

</div>

Thanks. I figured it out after looking through the PluginManager code. I  
just added a releases folder to the project on GitHub and built the zip in  
there. That seems to work.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [May 3, 2013, 10:41pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/12 "2013-05-03T22:41:34Z")

</div>

If you add any binary to git, all its versions (you will be updating your  
project, right?) will be download when you clone the repository in the  
history. It is better to separate the binaries from the source

Jorg introduced me to a site called [https://bintray.com/](https://bintray.com/)

--  
Ivan

On Fri, May 3, 2013 at 9:02 AM, Aall Spemmer [sssml2011@gmail.com](mailto:sssml2011@gmail.com) wrote:

> Thanks. I figured it out after looking through the PluginManager code. I  
> just added a releases folder to the project on GitHub and built the zip in  
> there. That seems to work.
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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:** [May 3, 2013, 11:59pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/13 "2013-05-03T23:59:51Z")

</div>

As Ivan said, a big -1 to have binaries within source code.  
Send it to sonatype using mvn release process. It's a bit tricky to create your first sonatype repo but after, it works like a charm.

More, maven users will be able to embed your plugin in their java app (using jar, not ZIP).

My 2 cents

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mai 2013 à 00:41, Ivan Brusic [ivan@brusic.com](mailto:ivan@brusic.com) a écrit :

If you add any binary to git, all its versions (you will be updating your project, right?) will be download when you clone the repository in the history. It is better to separate the binaries from the source

Jorg introduced me to a site called [https://bintray.com/](https://bintray.com/)

--  
Ivan

On Fri, May 3, 2013 at 9:02 AM, Aall Spemmer [sssml2011@gmail.com](mailto:sssml2011@gmail.com) wrote:

> Thanks. I figured it out after looking through the PluginManager code. I just added a releases folder to the project on GitHub and built the zip in there. That seems to work.
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [May 4, 2013, 12:44am UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/14 "2013-05-04T00:44:41Z")

</div>

I wrote a blog post about how easy it is to deploy ES plugin binaries to  
Bintray, because Github terminated the download service.

[http://jprante.github.io/2013/01/18/Bintray-for-Elasticsearch-plugins.html](http://jprante.github.io/2013/01/18/Bintray-for-Elasticsearch-plugins.html)

David, will plugin code reuse be supported in the future? I wonder how  
this can be accomplished - imagine you want only reuse plugin code, but  
not the plugin jar with the es-plugin.properties mechanism.

Of course, Bintray is also usable as a Maven repo, and I would love to  
see plugin developers being able to set up dependencies to reuse code  
from different plugins from different repos.

Jörg

Am 04.05.13 01:59, schrieb David Pilato:

> As Ivan said, a big -1 to have binaries within source code.  
> Send it to sonatype using mvn release process. It's a bit tricky to  
> create your first sonatype repo but after, it works like a charm.
> 
> More, maven users will be able to embed your plugin in their java app  
> (using jar, not ZIP).
> 
> My 2 cents
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 4 mai 2013 à 00:41, Ivan Brusic \<[ivan@brusic.com](mailto:ivan@brusic.com)  
> [mailto:ivan@brusic.com](mailto:ivan@brusic.com)\> a écrit :
> 
> If you add any binary to git, all its versions (you will be updating  
> your project, right?) will be download when you clone  
> the repository in the history. It is better to separate the binaries  
> from the source
> 
> Jorg introduced me to a site called [https://bintray.com/](https://bintray.com/)
> 
> --  
> Ivan
> 
> On Fri, May 3, 2013 at 9:02 AM, Aall Spemmer \<[sssml2011@gmail.com](mailto:sssml2011@gmail.com)  
> [mailto:sssml2011@gmail.com](mailto:sssml2011@gmail.com)\> wrote:
> 
> ```
> Thanks. I figured it out after looking through the PluginManager
> code. I just added a releases folder to the project on GitHub and
> built the zip in there. That seems to work.
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to elasticsearch+unsubscribe@googlegroups.com
> <mailto:elasticsearch%2Bunsubscribe@googlegroups.com>.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> ```
> 
> --  
> You received this message because you are subscribed to the Google  
> Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send  
> an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com)  
> [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google  
> Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send  
> an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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:** [May 4, 2013, 5:11am UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/15 "2013-05-04T05:11:56Z")

</div>

> David, will plugin code reuse be supported in the future?  
> IMHO, the easiest way to do it is to have 2 maven modules (+ pom parent project):

- core plugin
- es plugin  
Es plugin only contains es-plugin.properties and a dependency to core plugin.

About oss.sonatype, the cool thing is that your oss repo is synch'ed to maven central. No need to define specific repos.

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 4 mai 2013 à 02:44, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) a écrit :

I wrote a blog post about how easy it is to deploy ES plugin binaries to Bintray, because Github terminated the download service.

[http://jprante.github.io/2013/01/18/Bintray-for-Elasticsearch-plugins.html](http://jprante.github.io/2013/01/18/Bintray-for-Elasticsearch-plugins.html)

David, will plugin code reuse be supported in the future? I wonder how this can be accomplished - imagine you want only reuse plugin code, but not the plugin jar with the es-plugin.properties mechanism.

Of course, Bintray is also usable as a Maven repo, and I would love to see plugin developers being able to set up dependencies to reuse code from different plugins from different repos.

Jörg

Am 04.05.13 01:59, schrieb David Pilato:

> As Ivan said, a big -1 to have binaries within source code.  
> Send it to sonatype using mvn release process. It's a bit tricky to create your first sonatype repo but after, it works like a charm.
> 
> More, maven users will be able to embed your plugin in their java app (using jar, not ZIP).
> 
> My 2 cents
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 4 mai 2013 à 00:41, Ivan Brusic \<[ivan@brusic.com](mailto:ivan@brusic.com) [mailto:ivan@brusic.com](mailto:ivan@brusic.com)\> a écrit :
> 
> If you add any binary to git, all its versions (you will be updating your project, right?) will be download when you clone the repository in the history. It is better to separate the binaries from the source
> 
> Jorg introduced me to a site called [https://bintray.com/](https://bintray.com/)
> 
> --  
> Ivan
> 
> On Fri, May 3, 2013 at 9:02 AM, Aall Spemmer \<[sssml2011@gmail.com](mailto:sssml2011@gmail.com) [mailto:sssml2011@gmail.com](mailto:sssml2011@gmail.com)\> wrote:
> 
> Thanks. I figured it out after looking through the PluginManager  
> code. I just added a releases folder to the project on GitHub and  
> built the zip in there. That seems to work.
> 
> -- You received this message because you are subscribed to the Google  
> Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it,  
> send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com)  
> [mailto:elasticsearch%2Bunsubscribe@googlegroups.com](mailto:elasticsearch%2Bunsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com) [mailto:elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Aall\_Spemmer](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Aall\_Spemmer](https://discuss.elastic.co/u/Aall_Spemmer)\
**Post date:** [May 4, 2013, 10:21pm UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/16 "2013-05-04T22:21:22Z")

</div>

Thanks for the advice and the suggestion of using bintray. I have moved  
the binary to bintray.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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, 2:38am UTC](https://discuss.elastic.co/t/contributing-a-jms-river-plugin/11730/17 "2017-07-06T02:38:16Z")

</div>


