[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530111#comment-14530111
]
Shalin Shekhar Mangar commented on SOLR-7012:
---------------------------------------------
I propose that we piggy back on maven's archetype support and have Solr publish
its own solr-plugin archetype. Then anybody who wants to write a solr plugin
can execute e.g.
{code}
mvn archetype:generate -DgroupId=com.my.solrplugin -DartifactId=my-solr-plugin
-DarchetypeGroupId=org.apache.solr -DarchetypeArtifactId=solr-plugin
-DinteractiveMode=false
{code}
This will create project structure with a custom pom.xml with appropriate
defaults that we (Solr) can control.
> 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-sdk.patch, 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]
