Re: Parent POM, properties and scm problem

2007-08-07 Thread Eric Redmond
Might I suggest for the time being, to download and install the maven-pom-plugin ( http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-pom-plugin/) and manually manage the scm fields in the projects. I know it's a hack, but non-standard layouts tend to produce non-standard solutions.

Re: Parent POM, properties and scm problem

2007-08-06 Thread Jared Bunting
. -- Bryan -Original Message- From: Oscar Picasso [EMAIL PROTECTED] Sent: Wednesday, August 01, 2007 10:31 AM To: Maven Users List Subject: Re: Parent POM, properties and scm problem The current Maven behaviour is fine for multimodule projects. However I am trying to write

RE: Parent POM, properties and scm problem

2007-08-06 Thread Jörg Schaible
Oscar Picasso wrote on Wednesday, August 01, 2007 7:31 PM: The current Maven behaviour is fine for multimodule projects. However I am trying to write a organizational POM that all my projets would inherited and wanted to avoid duplication of the scm section. So in case of independent

Re: Parent POM, properties and scm problem

2007-08-02 Thread Oscar Picasso
: Wednesday, August 01, 2007 10:31 AM To: Maven Users List Subject: Re: Parent POM, properties and scm problem The current Maven behaviour is fine for multimodule projects. However I am trying to write a organizational POM that all my projets would inherited and wanted to avoid duplication

Re: Parent POM, properties and scm problem

2007-08-01 Thread Oscar Picasso
The current Maven behaviour is fine for multimodule projects. However I am trying to write a organizational POM that all my projets would inherited and wanted to avoid duplication of the scm section. So in case of independent projects it does not make sense to put all them inside the same trunk.

RE: Parent POM, properties and scm problem

2007-08-01 Thread Bryan Loofbourrow
- From: Oscar Picasso [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 01, 2007 10:31 AM To: Maven Users List Subject: Re: Parent POM, properties and scm problem The current Maven behaviour is fine for multimodule projects. However I am trying to write a organizational POM that all my projets

Re: Parent POM, properties and scm problem

2007-07-31 Thread Eric Redmond
Maven does this so that child module's scm can be defined once in the parent. scm connectionscm:svn:https://url/project/trunk /scm modules moduleChild Then the Child module's scm url is automatically set as: scm connectionscm:svn:https://url/project/trunk/Child /scm Which is the

Re: Parent POM, properties and scm problem

2007-07-30 Thread Oscar Picasso
I have also noticed the same behavior with the project url, the sit url and the scm url even if in the effective the corresponding properties are correct (without the artifactId appended). On 7/30/07, Oscar Picasso [EMAIL PROTECTED] wrote: Hi, In the parent POM I have the following: [...]