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]> wr

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 i

Re: [m2] parent poms and svn externals

2005-11-20 Thread Brett Porter
; Please comment and vote... > > 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 >

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 > tag has to include > ../build/pom.xml (and everyone will need > to know to check out 'build' along with whichever sub-project). And > the svn externals are no longer useful.

RE: [m2] parent poms and svn externals

2005-11-20 Thread Jeff Jensen
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 Maven discovers pom's in ../pom.xml, so if your layout > is different, you must ensure that

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 repositor

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-19 Thread Stephen Duncan
Child projects specify their parent POM using the tag instead of . A parent tag looks like this: com.myproject myproject 1.3-SNAPSHOT The parent POM is looked for in the repository, so, in your source structure, it can exist anywhere. -Stephen On 11/19/05, Wendy Smoak <[EMAIL PROT