[
https://issues.apache.org/jira/browse/LUCENE-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3944:
--------------------------------
Attachment: LUCENE-3944.patch
Patch implementing a new target {{filter-pom-templates}}, which places the POMs
under {{lucene/build/poms/}}. {{dist-maven}} pulls POMs from this location
instead of from each module's source directory. {{generate-maven-artifacts}}
under {{lucene/}} seems to work; I haven't tested much else.
There is an Ant problem, though: I have attempted to override {{dist-maven}} in
{{solr/common-build.xml}}, but it's being ignored in Solr modules, which are
instead using the {{dist-maven}} definition in {{lucene/common-build.xml}}. My
reading of the Ant docs makes me think this may be the intended behavior: only
the running build file's target definitions override those that are imported.
> ant clean should remove pom.xml's
> ---------------------------------
>
> Key: LUCENE-3944
> URL: https://issues.apache.org/jira/browse/LUCENE-3944
> Project: Lucene - Java
> Issue Type: Improvement
> Components: general/build
> Reporter: Chris Male
> Priority: Blocker
> Fix For: 3.6, 4.0
>
> Attachments: LUCENE-3944.patch
>
>
> Currently once the pom.xml's are in place, its hard to get them out. Having
> them can be a little trappy when you're trying to debug the bug. We should
> facilitate their removal during clean.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
