[
https://issues.apache.org/jira/browse/LUCENE-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245514#comment-13245514
]
Steven Rowe commented on LUCENE-3944:
-------------------------------------
bq. A nice improvement in the future would be if solr's common-build defined
filtered.pom.templates.dir to be under its own solr/build (rather than lucene's)
Where would {{modules/}} POMs go - each under its own build directory?
If we ever try to do this, I think Maven Ant Tasks' deploy target needs to be
able to access the parent and grandparent POMs, which (I think) means either
putting them into the user's local maven repository, or putting them at the
relative location given in the parent POM section of each POM. Maybe in order
to satisfy this the grandparent POM could be put in both places (or all places
if {{modules/}} need their own)?
> 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, 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]
