Re: [m2] parent poms and svn externals

2005-11-20 Thread Brett Porter
Right - though Maven discovers pom's in ../pom.xml, so if your layout is different, you must ensure that the parent is already installed in the repository (mvn install in the build directory in this case, or deployed to a remote repository accessible from the child project). - Brett On 11/20/05,

Re: [m2] parent poms and svn externals

2005-11-20 Thread Wendy Smoak
On 11/20/05, Brett Porter [EMAIL PROTECTED] wrote: Right - though Maven discovers pom's in ../pom.xml, so if your layout is different, you must ensure that the parent is already installed in the repository (mvn install in the build directory in this case, or deployed to a remote repository

RE: [m2] parent poms and svn externals

2005-11-20 Thread Jeff Jensen
: Sunday, November 20, 2005 12:31 PM To: Maven Users List Subject: Re: [m2] parent poms and svn externals On 11/20/05, Brett Porter [EMAIL PROTECTED] wrote: Right - though Maven discovers pom's in ../pom.xml, so if your layout is different, you must ensure that the parent is already installed

Re: [m2] parent poms and svn externals

2005-11-20 Thread Brett Porter
On 11/21/05, Wendy Smoak [EMAIL PROTECTED] wrote: It seems like we're going to lose that with m2. So far I think the parent tag has to include relativePath../build/pom.xml/relativePath (and everyone will need to know to check out 'build' along with whichever sub-project). And the svn

Re: [m2] parent poms and svn externals

2005-11-20 Thread Brett Porter
... http://jira.codehaus.org/browse/MNG-1471 -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Sunday, November 20, 2005 12:31 PM To: Maven Users List Subject: Re: [m2] parent poms and svn externals On 11/20/05, Brett Porter [EMAIL PROTECTED] wrote: Right - though

Re: [m2] parent poms and svn externals

2005-11-20 Thread Wendy Smoak
On 11/20/05, Brett Porter [EMAIL PROTECTED] wrote: No, that's not the case. Someone just needs to deploy that root project. Relative path is just a hint for using a multiproject checkout structure so that if you edit it locally it gets picked up. It still goes to the repository if it is not

Re: [m2] parent poms and svn externals

2005-11-20 Thread Brett Porter
You've got this corect - the modules are path based (in hindisght, maybe they should be repository references too - we'll look at implementing that in a backwards compatible way in 2.1). - Brett On 11/21/05, Wendy Smoak [EMAIL PROTECTED] wrote: On 11/20/05, Brett Porter [EMAIL PROTECTED] wrote:

[m2] parent poms and svn externals

2005-11-19 Thread Wendy Smoak
Struts uses svn externals to place /struts/build/trunk under each other sub-project, such as core. (Then a 'current' external to make it possible to check out all the sub-projects at once.) The result is a structure like this: /current/build /current/core /current/core/build Where those two

Re: [m2] parent poms and svn externals

2005-11-19 Thread Stephen Duncan
Child projects specify their parent POM using the parent tag instead of extends. A parent tag looks like this: parent groupIdcom.myproject/groupId artifactIdmyproject/artifactId version1.3-SNAPSHOT/version /parent The parent POM is looked for in the repository, so, in your source