Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.0-beta-1
-
Labels:None
-
Number of attachments :
Description
Imagine that I have a project with several modules. I'd like to run jdiff in one of the modules. This module doesn't have a different release cycle than the project and thus doesn't have a trunk, branches and tags SCM urls. Only the project has.
The <scm> of this module is:
<scm> <connection>scm:svn:svn://svn.codehaus.org/cargo/cargo/trunk/core/api/container</connection> <url>http://svn.cargo.codehaus.org/</url> </scm>
The reporting section is
<reporting> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jdiff-maven-plugin</artifactId> <configuration> <oldTag>0.8</oldTag> </configuration> </plugin> </plugins> </reporting>
When I execute the jdiff plugin it tries to checkout from svn://svn.codehaus.org/cargo/cargo/trunk/core/api/tags/0.8 which doesn't exist. The correct SVN url should be: svn://svn.codehaus.org/cargo/cargo/tags/0.8/core/api/container/.
I can't figure a way to make the jdiff plugin use this url, even if I use svnTagBase.
One solution would be to look for "trunk" and replace it with "tags/$
{oldTag}" and also offer a generic solution by proposing a <scmTemplateUrl> where the tag would be represented by some token (say @TAG@). Users would be able to write:
<scmTemplateUrl>svn://svn.codehaus.org/cargo/cargo/tags/@TAG@/core/api/container/</scmTemplateUrl>
Thanks
I think I can close this issue, just need to verify it. The plugin is using a new strategy: it's not calculating the tag, but it tries to do a buildFromRepository and next it reads the scm-connection from the MavenProject.