Hi Mike,
> As of Maven 3 parent POMs are no longer searched for in the
reactor.
This sentence as conclusion of the cited web-site is simply wrong...
Excerpt of the cited web site:
Maven 3 no longer resolves parent POMs from the local project checkout
unless the child POM's <relativePath> element is accurate, whether
explicitly given or using the default value.
You must be aware of the part "...unless the child POM's <relativePath
element is accurate, whether explicitly given or using the default value.".
The default value of a relativePath is "../pom.xml" which adresses the
parent in the parent folder inside the folder structure on the file system.
I'd like to understand more about the motivations behind this
change. Are there any pointers to previous discussion?
The second part of the explanation explains an example:
In Maven 2, building the child project in isolation could fail while the
reactor build would succeed to resolve the parent.
This means in Maven 2 it could happen if you try to build a child to
fail, cause the parent pom is resolved against the local repository
instead from the filesystem...
Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
