maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Sesterhenn (JIRA) <j...@codehaus.org>
Subject [jira] (MCHANGELOG-79) Add support for "tag" type report of Subversion
Date Fri, 12 Jul 2013 08:30:05 GMT

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

Jörg Sesterhenn commented on MCHANGELOG-79:
-------------------------------------------

Could you please release this? I'd prefer a solution with minor Bugs to no solution at all.

I would wish for an option to generate the report on all tags found up to the current revision
(complete changeloghistory) where the tags would be either sorted by revision or maven-style
(i.e. given all found tags have the format "artifactId-version" than tags would be sorted
by version just like maven would do). But I guess I better bring up another issue for this
improvement request...
                
> Add support for "tag" type report of Subversion
> -----------------------------------------------
>
>                 Key: MCHANGELOG-79
>                 URL: https://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,
MCHANGELOG-79-Add-support-for-svn-tag-diffs-New-Patch-no-BranchBase-property.patch, SvnTag_changelog.patch,
svntag-report-sample.JPG
>
>
>  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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message