[jira] [Commented] (SOLR-7012) add an ant target to package a plugin into a jar
[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15677995#comment-15677995
]
Cassandra Targett commented on SOLR-7012:
-
Changed this from being a sub-task of SOLR-5200, since it doesn't seem directly
related to a Config API and all the other sub-tasks there are completed.
> 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: Improvement
>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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7012) add an ant target to package a plugin into a jar
[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7012) add an ant target to package a plugin into a jar
[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7012) add an ant target to package a plugin into a jar
[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294099#comment-14294099
]
Noble Paul commented on SOLR-7012:
--
what would be the steps involved to write and package user's code?
will it be easier than the patch submitted by ishan?
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7012) add an ant target to package a plugin into a jar
[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14293393#comment-14293393
]
Ishan Chattopadhyaya commented on SOLR-7012:
Assert would need ant-contrib jars, and a base ant installation wouldn't work.
The script was to convert something like my.plugin.pkg to my/plugin/pkg
(replace dot with slash) so that it can be used in the fileset path for the
jar. Alternative to using that script is to use propertyregex tag, but, for
that too, the ant-contrib jars are needed.
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7012) add an ant target to package a plugin into a jar
[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14293385#comment-14293385
]
Noble Paul commented on SOLR-7012:
--
use assert to ensure that those properties are set
http://ant-contrib.sourceforge.net/tasks/tasks/assert_task.html
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7012) add an ant target to package a plugin into a jar
[
https://issues.apache.org/jira/browse/SOLR-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
