[ 
http://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196498#action_196498
 ] 

Dave Meibusch commented on MCHANGELOG-79:
-----------------------------------------

Minor issue with this patch: the StartVersion and EndVersion are not correctly 
read in from the change set XML file.
Tracked this down to ChangeLogHandler class, it looks for startTag and endTag 
attributes rather than startVersion / endVersion.

The symptoms are that the report, if reading from pre-generated XML file with 
have heading "Changes since project creation" rather than expected "Changes 
between...". Note that the File and Developer Activity reports re-read this 
file and exhibit this issue.

> Add support for "tag" type report of Subversion
> -----------------------------------------------
>
>                 Key: MCHANGELOG-79
>                 URL: http://jira.codehaus.org/browse/MCHANGELOG-79
>             Project: Maven 2.x Changelog Plugin
>          Issue Type: Improvement
>            Reporter: Kinugasa Noriko
>         Attachments: 
> MCHANGELOG-79_0001-Add-support-for-svn-tag-diffs.-Redo-the-original-MCH.patch,
>  svntag-report-sample.JPG, SvnTag_changelog.patch
>
>
>  Currently, Changelog plugin don't support Subversion's tag.
>  This patch make  The "tag" type report available even if you are using 
> Subversion.
>  This gets each revision of tags in Subversion system, and generates the 
> log-report between those revisions.
> For example, assume you have following repositoy structure:
> {noformat}
> http://example.com/svn/project
>          +trunk/
>          |    +src/
>          |      ...
>          +tags/
>          |    +1.0/
>          |    +1.1/
>          |    +1.2/
>          |    +2.0/
>          |    +2.1/
>          +branches/
>               +1.x/
> {noformat}
> To generate svn log's between 1.1 and 1.2 tag in 1.x branch:
>   [pom.xml]
> {code:xml}
>   ...
>   <!-- Subversion repositoy -->
>   <scm>
>     <!-- svn connection -->
>     <connection>scm:svn:http://example.com/svn/project</connection>
>   </scm>
>   ...
>   <reporting>
>     <plugins>
>       <!-- changelog-plugin -->
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-changelog-plugin</artifactId>
>         <version>2.2.1</version>
>         <configuration>
>           <!-- type is "tag" -->
>           <type>tag</type>
>           <tags>
>             <!-- between 1.1 and 1.2 tag -->
>             <tag implementation="java.lang.String">1.2</tag>
>             <tag implementation="java.lang.String">1.1</tag>
>           </tags>
>           <!-- in 1.x branch -->
>           <branchBase>branches/1.x</branchBase>
>           <!-- encoding -->
>           <outputEncoding>Windows-31J</outputEncoding>
>         </configuration>
>       </plugin>
>     </plugins>
>   </reporting>
>   ...
> {code} 
>  To generate svn log-report between 2.1 and 2.0 tag in trunk:
>  [pom.xml]
> {code:xml}
>  ...
>  <!-- Subversion repositoy -->
>   <scm>
>     <!-- svn connection -->
>     <connection>scm:svn:http://example.com/svn/project</connection>
>   </scm>
>   ...
>   <reporting>
>     <plugins>
>       <!-- changelog-plugin -->
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-changelog-plugin</artifactId>
>         <version>2.2.1</version>
>         <configuration>
>           <!-- type is "tag" -->
>           <type>tag</type>
>           <tags>
>             <!-- between 2.1 and 2.0 tag -->
>             <tag implementation="java.lang.String">2.0</tag>
>             <tag implementation="java.lang.String">2.1</tag>
>           </tags>
>           <!-- in trunk (Default brancheBase is trunk. So, branchBase
>                element is optional when to use trunk. ) -->
>           [<branchBase>trunk</branchBase>]
>           <!-- encoding -->
>           <outputEncoding>Windows-31J</outputEncoding>
>         </configuration>
>       </plugin>
>     </plugins>
>   </reporting>
>   ...
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to