[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293697#comment-14293697
]
Erik Hatcher commented on SOLR-7012:
------------------------------------
IMO, this "SDK" of sorts needs to be separate from Solr's own build. But
connected in that it needs to leverage the common-build infrastructure. I've
done this sort of thing like this
https://gist.github.com/erikhatcher/3aa0b40a6a3547d5405c - I've morphed it
slightly and pasted here:
{code}
<?xml version="1.0"?>
<project name="solr-development-kit" default="default">
<description>
Solr Development Kit
</description>
<property name="lucene.root" location="lucene-solr-5.0.0"/>
<property name="solr.root" location="${lucene.root}/solr"/>
<property name="build.dir" location="build"/>
<import file="${solr.root}/contrib/contrib-build.xml"/>
</project>
{code}
> 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]
