You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Ersin Er <er...@gmail.com> on 2006/01/26 05:48:54 UTC
pom: relativePath element in parent
Hi all,
I have a question, in fact a confirmation, about the difference
between specifying a relativePath in parent and specifying a project
with groupId and artifactId. Does maven work offline when we specify a
relativePath and online when we do it the other way? Is this the
working scheme?
Thanks.
--
Ersin
Re: pom: relativePath element in parent
Posted by dan tran <da...@gmail.com>.
first it looks for parent in relative path, default is one directory above.
and yes, in your child pom, you must specify gid and aid of the parent
-D
On 1/25/06, Ersin Er <er...@gmail.com> wrote:
>
> Ok, is it supposed to use gid-aid and relativePath exclusively? When I
> remove gid and aid and only specify relativePath the build fails. Is
> this the intended behaviour?
>
> Thanks.
>
> On 1/26/06, dan tran <da...@gmail.com> wrote:
> > Maven always looks for parent in local file system first, as long as the
> > local pom matches
> > with what the child project needs ( ie artifactid, groupid, version).
> >
> > But dont think it is working that way fully yet
> > http://jira.codehaus.org/browse/MNG-740
> >
> > Please vote for that JIRA ;-)
> >
> > -Dan
> >
> >
> > On 1/25/06, Ersin Er <er...@gmail.com> wrote:
> > >
> > > Hi all,
> > >
> > > I have a question, in fact a confirmation, about the difference
> > > between specifying a relativePath in parent and specifying a project
> > > with groupId and artifactId. Does maven work offline when we specify a
> > > relativePath and online when we do it the other way? Is this the
> > > working scheme?
> > >
> > > Thanks.
> > >
> > > --
> > > Ersin
> > >
> >
> >
>
>
> --
> Ersin
>
Re: pom: relativePath element in parent
Posted by Ersin Er <er...@gmail.com>.
Ok, is it supposed to use gid-aid and relativePath exclusively? When I
remove gid and aid and only specify relativePath the build fails. Is
this the intended behaviour?
Thanks.
On 1/26/06, dan tran <da...@gmail.com> wrote:
> Maven always looks for parent in local file system first, as long as the
> local pom matches
> with what the child project needs ( ie artifactid, groupid, version).
>
> But dont think it is working that way fully yet
> http://jira.codehaus.org/browse/MNG-740
>
> Please vote for that JIRA ;-)
>
> -Dan
>
>
> On 1/25/06, Ersin Er <er...@gmail.com> wrote:
> >
> > Hi all,
> >
> > I have a question, in fact a confirmation, about the difference
> > between specifying a relativePath in parent and specifying a project
> > with groupId and artifactId. Does maven work offline when we specify a
> > relativePath and online when we do it the other way? Is this the
> > working scheme?
> >
> > Thanks.
> >
> > --
> > Ersin
> >
>
>
--
Ersin
Re: pom: relativePath element in parent
Posted by dan tran <da...@gmail.com>.
Maven always looks for parent in local file system first, as long as the
local pom matches
with what the child project needs ( ie artifactid, groupid, version).
But dont think it is working that way fully yet
http://jira.codehaus.org/browse/MNG-740
Please vote for that JIRA ;-)
-Dan
On 1/25/06, Ersin Er <er...@gmail.com> wrote:
>
> Hi all,
>
> I have a question, in fact a confirmation, about the difference
> between specifying a relativePath in parent and specifying a project
> with groupId and artifactId. Does maven work offline when we specify a
> relativePath and online when we do it the other way? Is this the
> working scheme?
>
> Thanks.
>
> --
> Ersin
>