And if you check out the EAR in isolation, how should it behave? Break? It's an option, but one that has burned many a Maven 1 user. is there a reason you can't enter the groupId/artifactId as well/instead?
- Brett On 9/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > Right, thanks for your answer Kenney! > However, this is definitely not handy when you have a multi-module project > (for instance when you build an Ear). When your parent is part of the same > build process (using built-in reactor) and on the same file system, using > only "relativePath" would be far more handy. And when installing or > deploying the artifacts, this "relativePath" could be replaced by the real > artifactId/groupId/version values of the parent (which would make you pom > stand-alone). > > I've just seen there's an issue concerning this topic > (http://jira.codehaus.org/browse/MNG-624), but it targets version 2.1... > :o( > > Best Regards / Cordialement, > Fabrice BELLINGARD > DINQ/DSIN/INSI/EATE/IDVS/AIDV > (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] > > > > Kenney Westerhof > <[EMAIL PROTECTED] > rg> Pour > Maven Users List > 29/09/2005 15:28 <[email protected]> > cc > > Veuillez Objet > répondre à Re: [M2] How to use "relativePath" > Maven Users List of <parent> in a pom? > <[EMAIL PROTECTED] > che.org> > > > > > > > > > On Thu, 29 Sep 2005 [EMAIL PROTECTED] wrote: > > Hi, > > > Hi, > > > > I've seen that there's a "relativePath" attribute for the "parent" > element > > of the pom. According to the documentation, this is "the relative path of > > the parent-pom within the project hierarchy". If this property exists, I > > guess this allows to discover the parent pom without specifying the > > version, the artifactId and the groupId of the parent, which would be > > _very_ handy. However, I get the following error when launching maven: > > "Missing groupId element from parent element". > > > > So my question is: is this property working? I guess no: > > http://jira.codehaus.org/browse/MNG-1012 (which hasn't been assigned yet) > > But maybe this doesn't work this way. So my second question is: how does > > this property work? > > I'm not entirely up-to-speed on this new feature, but AFAIK the > artifactId and groupId are mandatory in a <parent> element (version too > IIRC). > POMs should be able to be used stand-alone. A client that uses your pom > wouldn't know where to look for that parent pom, since the directory > structure on ibiblio is not quite the same as the project tree structure. > > Before this attribute was in, m2 always checked ../pom.xml to see if it > matched the declared parent. If so, it used that (and the data in > target/*) instead of going to your local/remote repositories for the pom. > I guess this attribute is just an extension to that, so you can specify > other locations for your parent project than ../. > > Other m2 devs - jump in if this is incorrect! > > -- Kenney > > > Thanks in advance for your answers! > > > > Best Regards / Cordialement, > > Fabrice BELLINGARD > > DINQ/DSIN/INSI/EATE/IDVS/AIDV > > (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > Kenney Westerhof > http://www.neonics.com > GPG public key: http://www.gods.nl/~forge/kenneyw.key > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
