[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297014#comment-14297014
]
Erik Hatcher commented on SOLR-7012:
------------------------------------
bq. what would be the steps involved to write and package user's code? will it
be easier than the patch submitted by ishan?
Developer would create a directory structure (anywhere they like, ideally
*outside* of the Lucene/Solr source tree) the same as any of our contrib/
modules, put this build.xml file there, and make sure the pointer to the root
of the Lucene source tree (or plugin SDK tree) is right. We could automate
this a bit with an "SDK" directory in our distro that would generate a skeleton
project directory for them.
Looks like the patch here requires the plugin to be *in* the Lucene source
tree, which is not ideal. Developers would want to have their own custom code
in their own managed code directories/systems.
> add an ant target to package a plugin into a jar
> ------------------------------------------------
>
> Key: SOLR-7012
> URL: https://issues.apache.org/jira/browse/SOLR-7012
> Project: Solr
> Issue Type: Sub-task
> Reporter: Noble Paul
> Assignee: Noble Paul
> Attachments: SOLR-7012.patch, SOLR-7012.patch, SOLR-7012.patch
>
>
> Now it is extremely hard to create plugin because the user do not know about
> the exact dependencies and their poms
> we will add a target to solr/build.xml called plugin-jar
> invoke it as follows
> {code}
> ant -Dplugin.package=my.package -Djar.location=/tmp/my.jar plugin-jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
