[ 
https://jira.codehaus.org/browse/MJDIFF-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283449#comment-283449
 ] 

Robert Scholte commented on MJDIFF-6:
-------------------------------------

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.

> Make it work on modules of a project
> ------------------------------------
>
>                 Key: MJDIFF-6
>                 URL: https://jira.codehaus.org/browse/MJDIFF-6
>             Project: Maven 2.x JDiff Plugin
>          Issue Type: Improvement
>            Reporter: Vincent Massol
>
> 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:
> {code:xml}
>   <scm>
>     
> <connection>scm:svn:svn://svn.codehaus.org/cargo/cargo/trunk/core/api/container</connection>
>     <url>http://svn.cargo.codehaus.org/</url>
>   </scm>
> {code}
> The reporting section is
> {code:xml}
>   <reporting>
>     <plugins>
>       <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>jdiff-maven-plugin</artifactId>
>         <configuration>
>           <oldTag>0.8</oldTag>
>         </configuration>
>       </plugin>
>     </plugins>
>   </reporting>
> {code}
> 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:
> {code:xml}
> <scmTemplateUrl>svn://svn.codehaus.org/cargo/cargo/tags/@TAG@/core/api/container/</scmTemplateUrl>
> {code}
> Thanks

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to