This is deep down in the maven-release code, so no, you don't have to adjust it.

Why are you using relativePath? If you remove it and do a mvn install the super 
pom is copied to your local repository and found from there.

With regards,

Nick Stolwijk

-----Original Message-----
From: javijava [mailto:[EMAIL PROTECTED]
Sent: Fri 12/14/2007 12:46 PM
To: users@maven.apache.org
Subject: RE: FATAL ERROR on release:prepare  with a super-pom
 



>De code at the linenumber is:
>
        if ( trunkPath.endsWith( "/" ) )
        {
            trunkPath = trunkPath.substring( 0, trunkPath.length() - 1 );
        }
        if ( tagPath.endsWith( "/" ) )
        {
            tagPath = tagPath.substring( 0, tagPath.length() - 1 );
        }
>

.Where are placed this lines? in a maven-configuration fike?
.i must modify this..or is only the way that maven work with paths?


>Which will throw an exception if your trunkPath or tagPath is empty.
Is possible, that the <parent> tags in each sub-project are wrong?

i have the super-pom in a folder like the sub projects (same level), an
example of tags:

<parent>
                   <groupId>xxx</groupId>
                   <artifactId>super-pom</artifactId> 
                   <version>0.1-SNAPSHOT</version>
                   <relativePath>../super-pom/pom.xml</relativePath>
</parent>

Thanks 4 the reply Nick.





-- 
View this message in context: 
http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14334423.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to