lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3944) ant clean should remove pom.xml's
Date Tue, 03 Apr 2012 17:22:25 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message