Re: Referencing a parent POM without relativePath

Hi Eric everyone, I still think the userFriendlytrue/userFriendly version of Maven would just do the right thing when there is no relativePath/ element, and there is no ../pom.xml. I agree. Note that there is an issue for it already: http://jira.codehaus.org/browse/MNG-4687 Regards

Re: Referencing a parent POM without relativePath

On Mon, Nov 26, 2012 at 11:58 AM, Curtis Rueden ctrue...@wisc.edu wrote: Hi Eric everyone, I still think the userFriendlytrue/userFriendly version of Maven would just do the right thing when there is no relativePath/ element, and there is no ../pom.xml. I agree. Note that there is an issue

Re: Referencing a parent POM without relativePath

the right thing when there is no relativePath/ element, and there is no ../pom.xml. I agree. Note that there is an issue for it already: http://jira.codehaus.org/browse/MNG-4687 No, that's not what this issue says. This issue deals with the case where there IS a ../pom.xml but it's the wrong

Re: Referencing a parent POM without relativePath

, 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

Re: Referencing a parent POM without relativePath

I'd just like to echo Benson. You do not need the relativePath/ element if your environment is setup correctly. /Anders On Sat, Nov 24, 2012 at 4:48 AM, Eric Kolotyluk eric.koloty...@gmail.comwrote: On 2012-11-23 7:01 PM, Benson Margulies wrote: On Fri, Nov 23, 2012 at 8:45 PM, Eric

Referencing a parent POM without relativePath

I am playing around with getting our Corporate POM process working correctly, but running into problems. I have things configured so that people need to reference it without using relativePathblah/relativePath because I want them to get it from the repository and not from Perforce. In particular

Re: Referencing a parent POM without relativePath

Why don't you think that Maven will fish out a disconnected parent from Nexus? Many builds all over depend on this behavior. You just name the G/A/V and no relativePath, and Maven will download just as it would a dependency. If this isn't working for you we'd need more information to diagnose

Re: Referencing a parent POM without relativePath

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

Re: Referencing a parent POM without relativePath

On Fri, Nov 23, 2012 at 12:05 PM, Laird Nelson ljnel...@gmail.com wrote: On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies bimargul...@gmail.comwrote: You just name the G/A/V and no relativePath, and Maven will download just as it would a dependency. Well, not exactly

Re: Referencing a parent POM without relativePath

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

Re: Referencing a parent POM without relativePath

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

Re: Referencing a parent POM without relativePath

On Fri, Nov 23, 2012 at 12:11 PM, Anders Hammar and...@hammar.net wrote: Well, the corp pom should not be in the parent folder of any project. It's a standalone project. Yes; sorry if I contributed noise--my point was only to call attention to what the absence of relativePath meant

Re: Referencing a parent POM without relativePath

I tried putting relativePath/ in my POM, but it does not fix things. parent groupIdcom/groupId artifactIdkodak/artifactId version0.0.11-SNAPSHOT/version relativePath/ /parent I still get C:\Users\Eric\workspace\tree-combo-boxmvn clean [INFO] Scanning for projects

Re: Referencing a parent POM without relativePath

DOH! I retract that previous message. I forgot to open my VPN connection first. Putting relativePath/ in the POM does work! So, would it be unreasonable if Maven treated the absence of the relativePath element the same as relativePath/. That would make it more user friendly as far as I am

Re: Referencing a parent POM without relativePath

I had also discovered the difference between the missing vs. empty relativePath element. Although it was initially disconcerting that I had to specify an empty relativePath element to get what I assumed was the most reasonable behavior, I can also see the logic of the alternative with the default

Re: Referencing a parent POM without relativePath

OK, I have added the following to our Corporate POM. Hopefully I, and others, won't fall into this trap again. I still think the userFriendlytrue/userFriendly version of Maven would just do the right thing when there is no relativePath/ element, and there is no ../pom.xml. I can see no value

Re: Referencing a parent POM without relativePath

On 23/11/2012 3:22 PM, Eric Kolotyluk wrote: Unknown host repository.ca.kodak.com What is causing that? -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102

Re: Referencing a parent POM without relativePath

there is no relativePath/ element, and there is no ../pom.xml. I can see no value in the current Maven behavior of throwing an error the way it does. Eric, It does what you want. If it is not doing it for you, there's something wrong with your environment. None of our POMs have explicit

Re: Referencing a parent POM without relativePath

On Fri, Nov 23, 2012 at 10:00 PM, Ron Wheeler rwhee...@artifact-software.com wrote: On 23/11/2012 3:22 PM, Eric Kolotyluk wrote: Unknown host repository.ca.kodak.com What is causing that? Indeed this needs to be sorted first. -- Ron Wheeler President Artifact Software Inc email:

Re: Referencing a parent POM without relativePath

This problem is resolved. I forgot to bring up my VPN connections, so my local system could not see the Nexus server. I apologize for the confusion. Cheers, Eric On 2012-11-23 7:02 PM, Benson Margulies wrote: On Fri, Nov 23, 2012 at 10:00 PM, Ron Wheeler rwhee...@artifact-software.com wrote:

Re: Referencing a parent POM without relativePath

of Maven would just do the right thing when there is no relativePath/ element, and there is no ../pom.xml. I can see no value in the current Maven behavior of throwing an error the way it does. Eric, It does what you want. If it is not doing it for you, there's something wrong with your

Understand need for relativePath/ in parent references?

at ... instead of groupid:java-project-parent, please verify your project structure @ line 7, column 10 It didn't take me long to figure out that I had to add relativePath/ to my parent blocks. That fixed the problem. However, it seems odd that I had to do this. This seems counterintuitive

RE: Understand need for relativePath/ in parent references?

-Original Message- From: KARR, DAVID Sent: Friday, August 31, 2012 10:09 AM To: Maven Users List Subject: Understand need for relativePath/ in parent references? I have an app with a couple of modules, and I use a small parent hierarchy to define common settings. In source

Re: Understand need for relativePath/ in parent references?

: Friday, August 31, 2012 10:09 AM To: Maven Users List Subject: Understand need for relativePath/ in parent references? I have an app with a couple of modules, and I use a small parent hierarchy to define common settings. In source control, I have a somewhat flat hierarchy, where the main

m3: relativepath warning

Maven 3 emits a warning if the parent-pom relative path (../pom.xml) does not match the specified parent pom. However the ../pom.xml is a simple aggregator pom and the parent pom cannot be referenced from this location in subversion. Am I expected to put relativePath/ everywhere? Secondly, I vote

Re: m3: relativepath warning

Maven 3 emits a warning if the parent-pom relative path (../pom.xml) does not match the specified parent pom. However the ../pom.xml is a simple aggregator pom and the parent pom cannot be referenced from this location in subversion. Am I expected to put relativePath/ everywhere? Yes, that's

Re: m3: relativepath warning

and...@hammar.net wrote: Maven 3 emits a warning if the parent-pom relative path (../pom.xml) does not match the specified parent pom. However the ../pom.xml is a simple aggregator pom and the parent pom cannot be referenced from this location in subversion. Am I expected to put relativePath/ everywhere

mvn 3: parent.relativePath problem, but no relativePath element

, column 11 Line 6, column 11 is immediately after parent above (I removed whitespace for brevity so the line/column output is wrong here). I ran find . -name pom.xml | xargs grep 'relativePath' from the root, and there are no relative path elements in any of our pom files. How do I make

Re: mvn 3: parent.relativePath problem, but no relativePath element

is immediately after parent above (I removed whitespace for brevity so the line/column output is wrong here). I ran find . -name pom.xml | xargs grep 'relativePath' from the root, and there are no relative path elements in any of our pom files. Answering my own question, it looks like I hit http

Re: mvn 3: parent.relativePath problem, but no relativePath element

artifactIdfoo-api/artifactId parent artifactIdfoo-pomtype-api/artifactId groupIdcom.foobar/groupId version1.0-SNAPSHOT/version /parent [...] I ran find . -name pom.xml | xargs grep 'relativePath' from the root, and there are no relative path elements in any of our pom files

Skip checking for parent pom using relativePath

Hello maven-users, Is there a way to configure project pom.xml or in any other way suggest maven to skip checking for parent pom using relativePath? E.g. by setting relativePath to _skip or something similar. Regards, Stevo.

Re: maven relativepath in parent tag

relativePath must contain a relative path On Wednesday, September 9, 2009, SHAILJA shalja.ru...@gmail.com wrote: Can we have absolute path or environment variable in relativePath tag in parent tag, while inheriting pom.xml. I tried like giving --- /a/b/c/d --- and --- ${env.DIR}/c

maven relativepath in parent tag

Can we have absolute path or environment variable in relativePath tag in parent tag, while inheriting pom.xml. I tried like giving --- /a/b/c/d --- and --- ${env.DIR}/c/d --- envirornment variable is set DIR /a/b in both upper cases relative path is not resolved, and parent pom.xml

when is relativePath used?

My pom starts with parent artifactIdwaitlist-parent/artifactId groupIdedu.berkeley.ist.waitlist/groupId version1.1/version relativePath../../waitlist-parent/pom.xml/relativePath /parent When I run maven and the version inside the parent tags doesn't match

Re: when is relativePath used?

On Tue, Jul 14, 2009 at 6:56 PM, Rusty Wrightrusty.wri...@gmail.com wrote: My pom starts with   parent       artifactIdwaitlist-parent/artifactId       groupIdedu.berkeley.ist.waitlist/groupId       version1.1/version       relativePath../../waitlist-parent/pom.xml/relativePath   /parent

Re: when is relativePath used?

/artifactId groupIdedu.berkeley.ist.waitlist/groupId version1.1/version relativePath../../waitlist-parent/pom.xml/relativePath /parent When I run maven and the version inside the parent tags doesn't match what's in the parent's pom, it uses the pom from the repository (assuming there's

relativePath in parent section, if modules in different VOBs

version1.9.4/version !-- TODO how to define if in different VOB?-- relativePath../pom.xml/relativePath /parent This works fine, because the parent is referenced via its version But what about the relativePath? How can I setup a relative path, if the parent

RE: relativePath in parent section, if modules in different VOBs

/activation properties my_vob../my_vob/my_vob /properties /profile/profiles ... Then in your POM define the path as such: relativePath${my_vob}/relativePath You could also activate the profile based on the presence of a 'file' (i.e. the VOB root); I don't see any advantage

Re: Maven 2.0.7 and relativePath/

here. -Original Message- From: Dobri Kitipov [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 11:54 PM To: Maven Users List Subject: Re: Maven 2.0.7 and relativePath/ Hi Brian, thank you! You are right this placeholders in g/a/v are causing me lots of troubles. But anyway

RE: Maven 2.0.7 and relativePath/

and relativePath/ Hi, I think in this case it is possible to solve this if we use SNAPSHOT as a version. Regards, Dobri On Fri, May 9, 2008 at 4:38 AM, Brian E. Fox [EMAIL PROTECTED] wrote: The parents must be found before the property interpolation can occur and you essentially have a chicken or egg

Re: Maven 2.0.7 and relativePath/

PROTECTED] Sent: Friday, May 09, 2008 1:09 AM To: Maven Users List Subject: Re: Maven 2.0.7 and relativePath/ Hi, I think in this case it is possible to solve this if we use SNAPSHOT as a version. Regards, Dobri On Fri, May 9, 2008 at 4:38 AM, Brian E. Fox [EMAIL PROTECTED] wrote

Re: Maven 2.0.7 and relativePath/

@maven.apache.org Subject: Maven 2.0.7 and relativePath/ Hi all, I did not find a good explanation about the usage of relativePath/ in the net. I am interested if I have e.g.: parent groupIdcom.mycomp/groupId artifactIdmycomp-parent-pom/artifactId version${mycomp.version

RE: Maven 2.0.7 and relativePath/

and relativePath/ Hi Brian, thank you! You are right this placeholders in g/a/v are causing me lots of troubles. But anyway, can you give some more information why this is so? My impression is that this is something not deterministic. I mean sometime it may work, but some time not. regards, Dobri On Wed, May

RE: Maven 2.0.7 and relativePath/

It would only work I think if those properties are always defined on the command line or in your settings. -Original Message- From: Dobri Kitipov [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 11:54 PM To: Maven Users List Subject: Re: Maven 2.0.7 and relativePath/ Hi Brian

Maven 2.0.7 and relativePath/

Hi all, I did not find a good explanation about the usage of relativePath/ in the net. I am interested if I have e.g.: parent groupIdcom.mycomp/groupId artifactIdmycomp-parent-pom/artifactId version${mycomp.version}/version relativePath../../parent-pom/pom.xml

RE: Maven 2.0.7 and relativePath/

or the primary declaration of an artifact (project.group...etc) as this will surely cause you lots of headaches. -Original Message- From: Dobri Kitipov [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 7:50 AM To: users@maven.apache.org Subject: Maven 2.0.7 and relativePath/ Hi all, I

Re: relativePath

/relativePath-tf4140573.html#a11828087 Sent from the Continuum - Users mailing list archive at Nabble.com.

Re: relativePath

trunk-pom then this now works!! the superpom have the modules links , but modules don't need to have a relativePath from their parent. if i try to do directly the second structure doesn´t works, I thinks is because the artifacts are not in the local maven repository. well... how can I put some

Re: relativePath

Hi Jesse, First ,thanks to reply...but..i don't understand you relativePath is not used when the is some levels between parent pom modules? i create the superpom after the project to manage their dependence. If i understand you...all the artifacts (poms) may be in the svn repo

Re: relativePath

generally you don't need to use that relativePath tag.. and your second scenario still looks a little odd. I think maybe your not installing your superpom into the repository before you start building your project? Normally if your doing something like this with a company pom, then that pom

Parent and relativePath

Hi, I'm curious if it would be possible/feasible/in-line with maven philosophy to be able to specify in the parent/ tag ONLY relativePath/ tag or at least, if the relativePath/ is present be able to skip the version/ tag? That is, in the multi-module project, all the modules have to refer

Re: Parent and relativePath

Plotnicki, Grzegorz wrote: Hi, I'm curious if it would be possible/feasible/in-line with maven philosophy to be able to specify in the parent/ tag ONLY relativePath/ tag or at least, if the relativePath/ is present be able to skip the version/ tag? It would be impossible, because

Re: relativePath not working

tried 1 removing the relativePath setting altogether 2 relativePath../pom.xml/relativePath 3 relativePath../../parent_project/relativePath 4 relativePath../../parent_project/pom.xml/relativePath 5 relativePath [absolute path here] /relativePath I've double-checked the artifactId

Re: relativePath not working

the failure. Thanks http://www.nabble.com/file/7847/relative-path-of-parent.zip relative-path-of-parent.zip , Franz Davis Ford-2 wrote: Hi Adrian, I've tried nearly everything. Note, I'm using 2.0.6. I tried 1 removing the relativePath setting altogether 2 relativePath

relativePath not working

groupIdmy.org/groupId artifactIdparent/artifactId version1.0-SNAPSHOT/version relativePath../pom.xml/relativePath /parent groupIdmy.org/groupId artifactIdsub/artifactId packagingpom/packaging version1.0-SNAPSHOT/version anytime i issue any mvn command

RE: relativePath not working

in the same multi-module build 3) repository (However, in 2.0.4, there seems to be a bug prohibiting 1 from working in some scenerioes) Adrian From: Davis Ford [mailto:[EMAIL PROTECTED] Sent: Fri 4/13/2007 8:51 AM To: Maven Users List Subject: relativePath

Re: relativePath not working

Hi Adrian, I've tried nearly everything. Note, I'm using 2.0.6. I tried 1 removing the relativePath setting altogether 2 relativePath../pom.xml/relativePath 3 relativePath../../parent_project/relativePath 4 relativePath../../parent_project/pom.xml/relativePath 5 relativePath [absolute

Re: relativePath not working

relative-path-of-parent.zip , Franz Davis Ford-2 wrote: Hi Adrian, I've tried nearly everything. Note, I'm using 2.0.6. I tried 1 removing the relativePath setting altogether 2 relativePath../pom.xml/relativePath 3 relativePath../../parent_project/relativePath 4 relativePath

RE: relativePath not working

: relativePath not working Good day, I just tried creating a simple project with inheritance and I cannot duplicate your problem. I ran mvn validate, mvn package, mvn compiler:compile and it builds just fine with my Maven 2.0.6, and Java 1.5.0_11, running under Windows XP. I've attached here

Re: relativePath not working

, I've tried nearly everything. Note, I'm using 2.0.6. I tried 1 removing the relativePath setting altogether 2 relativePath../pom.xml/relativePath 3 relativePath../../parent_project/relativePath 4 relativePath../../parent_project/pom.xml/relativePath 5 relativePath [absolute path

Problem /w RelativePath and Multiple level Inheritance

the parent POM. I'm using relativePath to indicate where the son should search for his parent. Here is the code: Main pom: ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdorg.migs.ejemplos/groupId artifactIdmaven-test/artifactId version0.0.1/version packagingpom

Re: Problem /w RelativePath and Multiple level Inheritance

the parent POM. I'm using relativePath to indicate where the son should search for his parent. Here is the code: Main pom: ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdorg.migs.ejemplos/groupId artifactIdmaven-test/artifactId version0.0.1/version

Re: Problem /w RelativePath and Multiple level Inheritance

meaning my local repository is clean w/o anyone of my artifacts) from the main I get and error because son artifact cant find the parent POM. I'm using relativePath to indicate where the son should search for his parent. Here is the code: Main pom: ?xml version=1.0 encoding=UTF-8? project

relativePath in parent not honored

Hi All, Our organization has a pom hierarchy set up and the child poms refer to the parent pom using relativePath element. In the maven documentation, the following is clearly listed: Notice the relativePath element. It is not required, but may be used as a signifier to Maven to first search

Re: relativePath in parent not honored

, Himabindu (GE Healthcare) [EMAIL PROTECTED] To: users@maven.apache.org Sent: Friday, December 08, 2006 1:24 PM Subject: relativePath in parent not honored Hi All, Our organization has a pom hierarchy set up and the child poms refer to the parent pom using relativePath element. In the maven

[m2] Parent poms and relativePath

Can someone explain exactly how parent/relativePath works? I thought that Maven would use relativePath first, before looking in the local repository, but that's not what happens. With this structure: struts/current/pom/ -- struts-parent struts/current/action -- struts-action-parent

Re: [m2] Parent poms and relativePath

Do the versions match? The order is 1) running in the reactor 2) relativePath (default ../pom.xml) 3) local repository 4) remote repository However, the ids and version all must match. - Brett On 4/9/06, Wendy Smoak [EMAIL PROTECTED] wrote: Can someone explain exactly how parent/relativePath

Re: [m2] Parent poms and relativePath

Give this a try with 2.0.2 and the 2.0.4 RC... I believe this was a regression bug in 2.0.3. ;-) Wayne On 4/8/06, Wendy Smoak [EMAIL PROTECTED] wrote: Can someone explain exactly how parent/relativePath works? I thought that Maven would use relativePath first, before looking in the local

Re: [m2] Parent poms and relativePath

Smoak [EMAIL PROTECTED] wrote: Can someone explain exactly how parent/relativePath works? I thought that Maven would use relativePath first, before looking in the local repository, but that's not what happens. With this structure: struts/current/pom/ -- struts-parent struts

Re: [m2] Parent poms and relativePath

with 2.0.2 and the 2.0.4 RC... I believe this was a regression bug in 2.0.3. ;-) Wayne On 4/8/06, Wendy Smoak [EMAIL PROTECTED] wrote: Can someone explain exactly how parent/relativePath works? I thought that Maven would use relativePath first, before looking in the local repository

Re: [m2] Parent poms and relativePath

On 4/8/06, Brett Porter [EMAIL PROTECTED] wrote: Do the versions match? The order is 1) running in the reactor 2) relativePath (default ../pom.xml) 3) local repository 4) remote repository However, the ids and version all must match. Yes, the versions match: http://svn.apache.org/repos

Re: [m2] Multi-Project setup and relativePath

Hi, From how I understand on how the relativePath works, it is used for resolving the parent pom (being inside the parent tag). When you run mvn on a sub-module, mvn detects that the sub-module has a parent and mvn tries to resolve that using either the groupId:artifactId:version

RE: [m2] Multi-Project setup and relativePath

-Original Message- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 14, 2006 10:40 AM To: Maven Users List Subject: Re: [m2] Multi-Project setup and relativePath [...] So the approach is, if you want to use an artifact, then that artifact must have been

[m2] Multi-Project setup and relativePath

Hi maven-users! I've got a m2 project with several levels of sub-modules, held together by a main pom of packaging type pom. In each sub-module there is a parent entry pointing to the module above, including the relativePath tag pointing to ../ . I don't quite understand the use

[m2] Why does DefaultModelInheritanceAssembler ignore relativePath../relativePath or module...module definitions ?

Hi, I have severe problems with the flat project layout as described at http://maven.apache.org/guides/mini/guide-ide-eclipse.html at the end of the site. As it seems inheritance is not supporting the relative path and modules settings. Somewhere in here

Re: [m2] Why does DefaultModelInheritanceAssembler ignore relativePath../relativePath or module...module definitions ?

This probably should be the behaviour (as long as the SCM is laid out like your local copy is, which isn't strictly necessary, eg with SVN externals, but the same fallback is there - to specifically define the URL in the child POM). Would you like to file it in JIRA? - Brett On 11/24/05,

Re: [m2] parent's relativePath

I understand that artifactId and groupId are still required. But when I try using relativePath (and therefore removes the version element), Maven tells me that the version element of parent element is missing... Is it the default behaviour or I'm missing something? Best Regards / Cordialement

Re: [m2] parent's relativePath

The version is required too. Automatic versioning of the parent was deferred until 2.1. - Brett On 11/9/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I understand that artifactId and groupId are still required. But when I try using relativePath (and therefore removes the version element

RE: [m2] parent's relativePath

Thanks Dan, My problem seems similar/same as your MNG-740. I too have the parent pom not in a dir directly above the other components, but in a dir at the same level as the other components. In MNG-740, A doesn't build for me without the listed step 1: install root POM. The relativePath

RE: [m2] parent's relativePath

Brett, Based on your comment of MNG-624 on 11/6/05 7:56 pm, I'm either not using relativePath correctly, or can't/not supposed to at all. So is there a way to do what I tried below, or must the parent POM be in the repo? Does MNG-740 have any merit? Are there doc/clarification notes

Re: [m2] parent's relativePath

The docs on relativePath are lacking, and it really makes it quite deceptive. It is not extend from m1. What it does is modifies the behaviour of dan's first point. Basically, we have a concept of a universal source directory (more generally, a workspace) that is partially implemented - it means

RE: [m2] parent's relativePath

again for your help. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, November 06, 2005 8:37 PM To: Maven Users List Subject: Re: [m2] parent's relativePath The docs on relativePath are lacking, and it really makes it quite deceptive. It is not extend from m1

[m2] parent's relativePath

Hi, In parent, how does one use relativePath? I can only get POM inheritance to work if I have done a mvn install on the parent project. Then the component projects find it in the local private repo. I'm sure I just don't understand something yet. If there is docs on it, please give me an RTFM

Re: [m2] parent's relativePath

On 11/5/05, Jeff Jensen [EMAIL PROTECTED] wrote: Hi, In parent, how does one use relativePath? I can only get POM inheritance to work if I have done a mvn install on the parent project. Then the component projects find it in the local private repo. I'm sure I just don't understand something

[M2] How to use relativePath of parent in a pom?

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

Re: [M2] How to use relativePath of parent in a pom?

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

Re: [M2] How to use relativePath of parent in a pom?

Got it one Kenney. On 9/29/05, Kenney Westerhof [EMAIL PROTECTED] wrote: 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

Re: [M2] How to use relativePath of parent in a pom?

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

Re: [M2] How to use relativePath of parent in a pom?

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

Réf. : Re: [M2] How to use relativePath of parent in a pom?

cc VeuillezObjet répondre à Re: [M2] How to use relativePath Maven Users List