On Mon, Nov 26, 2012 at 3:37 PM, Curtis Rueden <[email protected]> wrote:
> However, I still think it worth noting, since it is a related issue with > Maven's behavior with respect to "doing the right thing" with relativePaths Indeed. For us, implicit relative path behavior (of ../pom.xml) shows up commonly when someone has a local ../pom.xml in their Subversion workspace that for some reason they haven't svn updated. Then they do a build of the ./pom.xml project (i.e. the child, not the parent) and get what seems to them to be bizarre results (i.e. that do not include the most recently deployed-to-the-corporate-repo ../pom.xml copy but instead occur because ../pom.xml is out of date and is silently being used by Maven instead of the (updated) Nexus/repo copy). An svn update of that ../pom.xml obviously fixes the issue (assuming that the version deployed to the repo is the same, of course). For this reason it seems that we would want to use <relativePath/> throughout our system. Does that sound right? Best, Laird -- http://about.me/lairdnelson
