maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <and...@hammar.net>
Subject Re: Referencing a parent POM without relativePath
Date Fri, 23 Nov 2012 17:11:06 GMT
Well, the corp pom should not be in the parent folder of any project. It's
a standalone project.

/Anders


On Fri, Nov 23, 2012 at 6:05 PM, Laird Nelson <ljnelson@gmail.com> wrote:

> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <bimargulies@gmail.com
> >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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message