I'm confused how the build can continue without the parent pom. I
wouldn't call the behavior "inconsistent", I would call it completely
indeterminate. The parent plugin could have managed dependencies, plugin
definitions, variable definitions, etc. that will simply make the build
not work correctly. I gather the fix for MNG-2196 was to create the
cache with the key being the groupId, artifactId and version.
Interestingly, I added another project cache for the fix to MNG-624, et
al. The key is the path to the pom, so having an incorrect relative path
makes the build impossible if you don't specify the parent project
version. Once this fix is in 2.1 I expect it will be common to leave the
version out of the parent element making specifying the correct parent
relative path even more important.
Ralph
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]