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 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
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> 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/
--
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%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.
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.
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.
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.
For more options, visit https://groups.google.com/groups/opt_out.