It's tied more to the decision of what role the Maven reactor session
plays in the build. The same question could be asked of JARs that were
just built but not installed.
I think as long as the POM is queued to be *built* in the current
reactor session it makes sense to use that, but pulling things from a
cache like now goes too far (it should only be caching repository
interactions).
- Brett
On 19/09/2008, at 5:45 AM, Shane Isbell wrote:
I'm wondering what people's take on
http://jira.codehaus.org/browse/MNG-2196for Maven 3.0 is. Continuing
with a build if a parent pom is not found on
the local file-system or in the repository is something that could
cause
inconsistent behavior between builds.
Thanks,
Shane
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
