You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kinugasa Noriko (JIRA)" <ji...@codehaus.org> on 2007/12/28 10:59:57 UTC

[jira] Created: (MCHANGELOG-79) Add support for "tag" type report of Subversion

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: 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:

http://example.com/svn/project
         +trunk/
         |    +src/
         |      ...
         +tags/
         |    +1.0/
         |    +1.1/
         |    +1.2/
         |    +2.0/
         |    +2.1/
         +branches/
              +1.x/

To generate svn log's between 1.1 and 1.2 tag in 1.x branch:
  [pom.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>
  ...
 

 To generate svn log-report between 2.1 and 2.0 tag in trunk:
 [pom.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>
  ...

-- 
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

        

[jira] Commented: (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220492#action_220492 ] 

Dennis Lundberg commented on MCHANGELOG-79:
-------------------------------------------

Jerome, I had a look at the patch file. It seems to be made from GIT. Can you supply a standard svn diff instead?

> 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

        

[jira] (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Tom Briers (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315221#comment-315221 ] 

Tom Briers commented on MCHANGELOG-79:
--------------------------------------

Hi,
I applied the patches on a personnel checkout and I do not think this is correct.

What seems to be done is the following:
  * get revision of tag A
  * get revision of tag B
  * execute svn --non-interactive log -v -r revA:revB svn://theUrlToTheRepositoryOfYourCurrentCheckout

I think the correct way is:
  * get revision of tag A
  * get revision of tag B
  * execute svn --non-interactive log -v -r revA:revB svn://theUrlToTheTagB


                
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Robin (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286416#comment-286416 ] 

Robin commented on MCHANGELOG-79:
---------------------------------

Is there any activity on this feature request? Where can I find a beta-build for testing?
                
> 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, 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Jerome Lacoste (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerome Lacoste updated MCHANGELOG-79:
-------------------------------------

    Attachment: MCHANGELOG-79_0001-Add-support-for-svn-tag-diffs.-Redo-the-original-MCH.patch

New version of the patch.

The original patch wasn't working for me when testing changelogs for various tags. The problem was caused by the way the SvnInfoCommand was used, and the way plexus-utils has evolved I guess: the executed command ended up being:

cd $workingDir$svnTag && ....

causing the command line to fail.

I've forked the SvnInfoCommand into an SvnInfoCommandExpanded and packaged it into the changelog plugin to make it quick to test the changes. The proper fix would be to propagate the changes of SvnInfoCommandExpanded into the maven-svm-provider-svn project.

I haven't tested all use cases specified by this patch and chose to let the original code as much as possible. I haven't added unit tests...

Let me know if you need further info/code.

> 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

        

[jira] (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Samuel Van Reeth (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Samuel Van Reeth updated MCHANGELOG-79:
---------------------------------------

    Attachment: MCHANGELOG-79-Add-support-for-svn-tag-diffs-New-Patch-no-BranchBase-property.patch

I created a new patch for this problem.

It is a new implementation, using the forked SvnInfoCommandExpanded class from Jerome Lacoste but without the SvnTrunkChangeLogCommand class and without the need for the branchBase property.
                
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MCHANGELOG-79:
--------------------------------------

    Description: 
 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}

  was:
 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:

http://example.com/svn/project
         +trunk/
         |    +src/
         |      ...
         +tags/
         |    +1.0/
         |    +1.1/
         |    +1.2/
         |    +2.0/
         |    +2.1/
         +branches/
              +1.x/

To generate svn log's between 1.1 and 1.2 tag in 1.x branch:
  [pom.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>
  ...
 

 To generate svn log-report between 2.1 and 2.0 tag in trunk:
 [pom.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>
  ...


> 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: 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

        

[jira] (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Samuel Van Reeth (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305384#comment-305384 ] 

Samuel Van Reeth edited comment on MCHANGELOG-79 at 8/2/12 4:03 PM:
--------------------------------------------------------------------

I created a new patch for this problem.

It is a new implementation, using the forked SvnInfoCommandExpanded class from Jerome Lacoste but without the SvnTrunkChangeLogCommand class and without the need for the branchBase property.

@Dave: check issue  MCHANGELOG-108 - read/write changelog.xml inconsistency
                
      was (Author: rodikal):
    I created a new patch for this problem.

It is a new implementation, using the forked SvnInfoCommandExpanded class from Jerome Lacoste but without the SvnTrunkChangeLogCommand class and without the need for the branchBase property.
                  
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Dave Meibusch (JIRA)" <ji...@codehaus.org>.
    [ 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

        

[jira] Updated: (MCHANGELOG-79) Add support for "tag" type report of Subversion

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MCHANGELOG-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MCHANGELOG-79:
--------------------------------------

    Patch Submitted: [Yes]

> 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