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.
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
onal pom by itself, and have your projects use it, from the
> > repository, as a parent for definition purposes, though not build
> > purposes.
> >
> > I'd be interested to know whether this works. It seems useful.
> >
> > -- Bryan
> >
> > -Orig
gt;
> -- Bryan
>
> -Original Message-
> 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 multimodul
al Message-
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
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.
Maven does this so that child module's scm can be defined once in the
parent.
scm:svn:https://url/project/trunk
Child
Then the Child module's scm url is automatically set as:
scm:svn:https://url/project/trunk/Child
Which is the convention for a multi-module project.
If your "Child"
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:
> [.
Hi,
In the parent POM I have the following:
[...]
http://localhost/repos/repo/${groupId}/${artifactId}/trunk
${scmConnection}
${scmConnection}
[...]
The child POM has nothing expect mandatory elements and the reference to the
parent POM. Both the child and the parent ar
sitzender des Aufsichtsrates
Heinz-Dieter Wendorff
Handelsregister
Amtsgericht Paderborn HRB 3270
[EMAIL PROTECTED]
09.05.2007 11:42
Bitte antworten an continuum-users
An: [EMAIL PROTECTED]
Kopie:
Thema: Antwort: Re: SCM Problem Continuum 1.0.3 & Ant
hi
I've been on 1.0.2 for a while and so thought I'd move on up to one of
the 1.1 rcs. I'm having trouble with rc3 though - when I do certain scm
operations it fails.
e.g. scm:update
scm:update:
[echo] Updating from SCM
BUILD FAILED
File.. file:/C:/Temp/.maven/cache/maven-scm-plugin-1.5/pl
t'
Subject: RE: [scm] Problem Running scm:bootstrap-project
Dsoes maven.conf.dir include ${basedir}? It looks like an additional
"edog" path is being added.
- Brett
> -Original Message-
> From: Norm Deane [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 28 January 2004 3:
Dsoes maven.conf.dir include ${basedir}? It looks like an additional "edog"
path is being added.
- Brett
> -Original Message-
> From: Norm Deane [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 28 January 2004 3:22 AM
> To: Maven Users List
> Subject: [scm] Prob
I'm trying to get the scm:bootstrap-project working and am running into a
problem.
I'm running 'maven scm:boostrap-project -Dmaven.scm.cvs.module=edog' from
c:\projects\crap\scm. The cvs checkout completes successfully (creating
c:\projects\crap\scm\edog) but when it tries to run my bootstrap go
14 matches
Mail list logo
