[
https://issues.apache.org/jira/browse/LUCENE-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055239#comment-13055239
]
Chris Male commented on LUCENE-3244:
------------------------------------
Actually I now see the ability to set the full jarfile in the contrib-uptodate
macro. I still want to avoid this, since it requires the invoker of the macro
to know the full path.
Instead I think having an optional 'project-name' property will suffice.
> Contrib/Module-uptodate assume name matches path and jar
> --------------------------------------------------------
>
> Key: LUCENE-3244
> URL: https://issues.apache.org/jira/browse/LUCENE-3244
> Project: Lucene - Java
> Issue Type: Bug
> Components: general/build
> Reporter: Chris Male
>
> With adding a new 'queries' module, I am trying to change the project name of
> contrib/queries to queries-contrib. However currently the contrib-uptodate
> assumes that the name property is used in the path and in the jar name.
> By using the name in the path, I must set the value to 'queries' (since the
> path is contrib/queries). However because the project name is now
> queries-contrib, the actual jar file will be
> lucene-queries-contrib-${version}.jar, not lucene-queries-${version}.jar, as
> is expected.
> Consequently I think we need to separate the path name from the jar name
> properties. For simplicity I think adding a new jar-name property will
> suffice, which can be optional and if omitted, is filled in with the name
> property.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
