The problem was fixed on Jan 12th and we have some tests that check the patch.
Do you have remove old maven-scm jars?
Where do you obtain the scm url?
You're not the only one that can't build some provider, but for now, we don't know why. We are
several people that run them without problem.
Here's what I've done :
1. Remove all maven-scm-*-1.0-beta-2.jar in continuum/lib . Replace them
with maven-scm-*-1.0-beta-3-20060115.041342-*.jar
2. Restart Continuum
3. Add parent in Continuum. module is also added. If I click on module,
Scm Url is scm:svn:svn://host/PROJECT/parent/module
Ok, it's a bug in
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/inheritance/DefaultModelInheritanceAssembler.java?rev=306518view=markup
in assembleScmInheritance method.
This method append parent scm connection url and artifactId
2006/1/24, Emmanuel Venisse [EMAIL PROTECTED]:
Ok, it's a bug in
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/inheritance/DefaultModelInheritanceAssembler.java?rev=306518view=markup
in assembleScmInheritance method.
This method
Emmanuel, I couldn't build maven-scm trunk, there are test failures in
maven-scm-provider-svn
I tried to put the deployed 20060115.041342 SNAPSHOTs in continuum/lib and
to use relativePath, but I got the same problem when I add the module in
Continuum : the URL is resolved as
Thanks Emmanuel, I'll try with maven-scm trunk then.
- Yann
2006/1/19, Emmanuel Venisse [EMAIL PROTECTED]:
Actually, you need to define scm url in all your modules if you want to
use relative path.
This problem is fixed in maven-scm trunk.
Emmanuel
Yann Le Du a écrit :
Hi,
In order
Actually, yes, I use artifactId for directory names, and had thought of this
solution. But I'd supposed it would give me :
scm:svn:svn://host/PROJECT/module/module
I can't try today, but will do on Monday and let you know. Thank you anyway.
- Yann
2006/1/19, Dennis Lundberg [EMAIL PROTECTED]:
How about this:
scm:svn:svn://host/PROJECT/${pom.artifactId}
This should work if you use the same name for the part in your svn
repository as their artifactIds.
This works. Unfortunately in our case the svn module does not match
the artifactId. It would be nice if they could deviate and
Yann, si t'es en ligne, c'est où sur RICFILED que tu précisent les options de
compil Javac pour MAVEN ??
Greg
De : Yann Le Du [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 20 janvier 2006 09:36
À : Maven Users List
Objet : Re: [m2] Multiprojects and inherited SCM
On 20/01/06, DELMOTTE Grégory [EMAIL PROTECTED] wrote:
Yann, si t'es en ligne, c'est où sur RICFILED que tu précisent les options de
compil Javac pour MAVEN ??
DTC _
Ps: catherine, est-ce que tu peux prendre du pain en sortant du boulot, merci.
Greg
Hi,
In order to ease Continuum use, we want to have the following project
structure :
~ PROJECT
~ +-- parent
~ +-- pom.xml
~ +-- module
~ +-- pom.xml
module has obviously parent for parent
parent defines this SCM URL :
scm:svn:svn://host/PROJECT/parent
In module, this is
Actually, you need to define scm url in all your modules if you want to use
relative path.
This problem is fixed in maven-scm trunk.
Emmanuel
Yann Le Du a écrit :
Hi,
In order to ease Continuum use, we want to have the following project
structure :
~ PROJECT
~ +-- parent
~ +--
Yann Le Du wrote:
Hi,
In order to ease Continuum use, we want to have the following project
structure :
~ PROJECT
~ +-- parent
~ +-- pom.xml
~ +-- module
~ +-- pom.xml
module has obviously parent for parent
parent defines this SCM URL :
scm:svn:svn://host/PROJECT/parent
In
13 matches
Mail list logo
