On Fri, Nov 23, 2012 at 12:11 PM, Anders Hammar <[email protected]> wrote: > Well, the corp pom should not be in the parent folder of any project. It's > a standalone project.
Well, precisely. 99% of the time you run 'svn co', and you get a directory in which ../pom.xml does not exist, and running mvn causes mvn to go out to repositories. If someone has a counter-example, we need a test case. > > /Anders > > > On Fri, Nov 23, 2012 at 6:05 PM, Laird Nelson <[email protected]> wrote: > >> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <[email protected] >> >wrote: >> >> > You just name the G/A/V and no relativePath, and Maven will download >> > just as it would a dependency. >> > >> >> Well, not exactly; if there is no <relativePath> element present, then >> Maven behaves as though <relativePath>../pom.xml</relativePath> were >> specified. If that file is a working copy that has not been refreshed from >> the SCM, then problems can ensue. >> >> I recall that someone mentioned specifying a relative path like this: >> >> <relativePath/> >> >> >> ...and that that was the only way to force Maven to truly resolve the pom >> from the repository, but I don't know if this is in fact true. >> >> Best, >> Laird >> >> -- >> http://about.me/lairdnelson >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
