You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alex Coyle (JIRA)" <ji...@codehaus.org> on 2011/08/18 00:33:32 UTC

[jira] Created: (MCHANGELOG-123) Patch with support for SCM provider implementations (similar to release plugin)

Patch with support for SCM provider implementations (similar to release plugin)
-------------------------------------------------------------------------------

                 Key: MCHANGELOG-123
                 URL: https://jira.codehaus.org/browse/MCHANGELOG-123
             Project: Maven 2.x Changelog Plugin
          Issue Type: Improvement
    Affects Versions: 2.2
            Reporter: Alex Coyle
         Attachments: maven-changelog-plugin-scmproviderimpl.patch

Hi,

The attached patch includes support for SCM 'provider implementations', similar to what is included in the Maven Release Plugin. I made this change because I wanted to use the Changelog plugin with the maven-scm-provider-svnjava project (an SVN provider that uses SVNkit):

http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/

I can confirm the patch works, and appears to generate a valid changelog report in the Maven site, when used with Maven 3.0.3 and a Maven project that follows this example POM structure:

{noformat}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  
  <modelVersion>4.0.0</modelVersion>
  <groupId>uk.co.example</groupId>
  <artifactId>example-project</artifactId>
  <packaging>pom</packaging>
  <version>1.0.0-SNAPSHOT</version>
  <name>Example Project</name>

  <scm>
    <url>http://example.co.uk/example-project</url>
    <connection>scm:svn:http://svn.example.co.uk/example-project/trunk</connection>
    <developerConnection>scm:svn:http://svn.example.co.uk/example-project/trunk</developerConnection>
  </scm>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-changelog-plugin</artifactId>
        <version>2.3-SNAPSHOT</version>
        <dependencies>
          <dependency>
            <groupId>com.google.code.maven-scm-provider-svnjava</groupId>
            <artifactId>maven-scm-provider-svnjava</artifactId>
            <version>1.13</version>
          </dependency>
        </dependencies>
      </plugin>
      <plugin>
        <artifactId>maven-site-plugin</artifactId>
        <version>3.0-beta-3</version>
        <configuration>
          <reportPlugins>
            <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-changelog-plugin</artifactId>
              <configuration>
                <issueIDRegexPattern>[A-Z]{2,}-\d+</issueIDRegexPattern>
                <issueLinkUrl>http://jira.example.co.uk</issueLinkUrl>
                <providerImplementations>
                  <svn>javasvn</svn>
                </providerImplementations>
              </configuration>
            </plugin>
          </reportPlugins>
        </configuration>
      </plugin>
    </plugins>
  </build>
  
</project>
{noformat}

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

        

[jira] (MCHANGELOG-123) Patch with support for SCM provider implementations (similar to release plugin)

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

Dan Rollo commented on MCHANGELOG-123:
--------------------------------------

Cool. Is a snapshot release of the 2.3 version published anywhere? (I could give it a try).

Also, any thoughts on when the 2.3 version might be released?

Thanks.
                
> Patch with support for SCM provider implementations (similar to release plugin)
> -------------------------------------------------------------------------------
>
>                 Key: MCHANGELOG-123
>                 URL: https://jira.codehaus.org/browse/MCHANGELOG-123
>             Project: Maven 2.x Changelog Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Alex Coyle
>            Assignee: Olivier Lamy
>             Fix For: 2.3
>
>         Attachments: maven-changelog-plugin-scmproviderimpl.patch
>
>
> Hi,
> The attached patch includes support for SCM 'provider implementations', similar to what is included in the Maven Release Plugin. I made this change because I wanted to use the Changelog plugin with the maven-scm-provider-svnjava project (an SVN provider that uses SVNkit):
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
> I can confirm the patch works, and appears to generate a valid changelog report in the Maven site, when used with Maven 3.0.3 and a Maven project that follows this example POM structure:
> {noformat}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
>   
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>uk.co.example</groupId>
>   <artifactId>example-project</artifactId>
>   <packaging>pom</packaging>
>   <version>1.0.0-SNAPSHOT</version>
>   <name>Example Project</name>
>   <scm>
>     <url>http://example.co.uk/example-project</url>
>     <connection>scm:svn:http://svn.example.co.uk/example-project/trunk</connection>
>     <developerConnection>scm:svn:http://svn.example.co.uk/example-project/trunk</developerConnection>
>   </scm>
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-changelog-plugin</artifactId>
>         <version>2.3-SNAPSHOT</version>
>         <dependencies>
>           <dependency>
>             <groupId>com.google.code.maven-scm-provider-svnjava</groupId>
>             <artifactId>maven-scm-provider-svnjava</artifactId>
>             <version>1.13</version>
>           </dependency>
>         </dependencies>
>       </plugin>
>       <plugin>
>         <artifactId>maven-site-plugin</artifactId>
>         <version>3.0-beta-3</version>
>         <configuration>
>           <reportPlugins>
>             <plugin>
>               <groupId>org.apache.maven.plugins</groupId>
>               <artifactId>maven-changelog-plugin</artifactId>
>               <configuration>
>                 <issueIDRegexPattern>[A-Z]{2,}-\d+</issueIDRegexPattern>
>                 <issueLinkUrl>http://jira.example.co.uk</issueLinkUrl>
>                 <providerImplementations>
>                   <svn>javasvn</svn>
>                 </providerImplementations>
>               </configuration>
>             </plugin>
>           </reportPlugins>
>         </configuration>
>       </plugin>
>     </plugins>
>   </build>
>   
> </project>
> {noformat}

--
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] Closed: (MCHANGELOG-123) Patch with support for SCM provider implementations (similar to release plugin)

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

Olivier Lamy closed MCHANGELOG-123.
-----------------------------------

    Resolution: Fixed

patch applied.
Thanks !

> Patch with support for SCM provider implementations (similar to release plugin)
> -------------------------------------------------------------------------------
>
>                 Key: MCHANGELOG-123
>                 URL: https://jira.codehaus.org/browse/MCHANGELOG-123
>             Project: Maven 2.x Changelog Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Alex Coyle
>            Assignee: Olivier Lamy
>         Attachments: maven-changelog-plugin-scmproviderimpl.patch
>
>
> Hi,
> The attached patch includes support for SCM 'provider implementations', similar to what is included in the Maven Release Plugin. I made this change because I wanted to use the Changelog plugin with the maven-scm-provider-svnjava project (an SVN provider that uses SVNkit):
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
> I can confirm the patch works, and appears to generate a valid changelog report in the Maven site, when used with Maven 3.0.3 and a Maven project that follows this example POM structure:
> {noformat}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
>   
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>uk.co.example</groupId>
>   <artifactId>example-project</artifactId>
>   <packaging>pom</packaging>
>   <version>1.0.0-SNAPSHOT</version>
>   <name>Example Project</name>
>   <scm>
>     <url>http://example.co.uk/example-project</url>
>     <connection>scm:svn:http://svn.example.co.uk/example-project/trunk</connection>
>     <developerConnection>scm:svn:http://svn.example.co.uk/example-project/trunk</developerConnection>
>   </scm>
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-changelog-plugin</artifactId>
>         <version>2.3-SNAPSHOT</version>
>         <dependencies>
>           <dependency>
>             <groupId>com.google.code.maven-scm-provider-svnjava</groupId>
>             <artifactId>maven-scm-provider-svnjava</artifactId>
>             <version>1.13</version>
>           </dependency>
>         </dependencies>
>       </plugin>
>       <plugin>
>         <artifactId>maven-site-plugin</artifactId>
>         <version>3.0-beta-3</version>
>         <configuration>
>           <reportPlugins>
>             <plugin>
>               <groupId>org.apache.maven.plugins</groupId>
>               <artifactId>maven-changelog-plugin</artifactId>
>               <configuration>
>                 <issueIDRegexPattern>[A-Z]{2,}-\d+</issueIDRegexPattern>
>                 <issueLinkUrl>http://jira.example.co.uk</issueLinkUrl>
>                 <providerImplementations>
>                   <svn>javasvn</svn>
>                 </providerImplementations>
>               </configuration>
>             </plugin>
>           </reportPlugins>
>         </configuration>
>       </plugin>
>     </plugins>
>   </build>
>   
> </project>
> {noformat}

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

        

[jira] (MCHANGELOG-123) Patch with support for SCM provider implementations (similar to release plugin)

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

Olivier Lamy commented on MCHANGELOG-123:
-----------------------------------------

try https://repository.apache.org/content/groups/snapshots/
                
> Patch with support for SCM provider implementations (similar to release plugin)
> -------------------------------------------------------------------------------
>
>                 Key: MCHANGELOG-123
>                 URL: https://jira.codehaus.org/browse/MCHANGELOG-123
>             Project: Maven 2.x Changelog Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Alex Coyle
>            Assignee: Olivier Lamy
>             Fix For: 2.3
>
>         Attachments: maven-changelog-plugin-scmproviderimpl.patch
>
>
> Hi,
> The attached patch includes support for SCM 'provider implementations', similar to what is included in the Maven Release Plugin. I made this change because I wanted to use the Changelog plugin with the maven-scm-provider-svnjava project (an SVN provider that uses SVNkit):
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
> I can confirm the patch works, and appears to generate a valid changelog report in the Maven site, when used with Maven 3.0.3 and a Maven project that follows this example POM structure:
> {noformat}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
>   
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>uk.co.example</groupId>
>   <artifactId>example-project</artifactId>
>   <packaging>pom</packaging>
>   <version>1.0.0-SNAPSHOT</version>
>   <name>Example Project</name>
>   <scm>
>     <url>http://example.co.uk/example-project</url>
>     <connection>scm:svn:http://svn.example.co.uk/example-project/trunk</connection>
>     <developerConnection>scm:svn:http://svn.example.co.uk/example-project/trunk</developerConnection>
>   </scm>
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-changelog-plugin</artifactId>
>         <version>2.3-SNAPSHOT</version>
>         <dependencies>
>           <dependency>
>             <groupId>com.google.code.maven-scm-provider-svnjava</groupId>
>             <artifactId>maven-scm-provider-svnjava</artifactId>
>             <version>1.13</version>
>           </dependency>
>         </dependencies>
>       </plugin>
>       <plugin>
>         <artifactId>maven-site-plugin</artifactId>
>         <version>3.0-beta-3</version>
>         <configuration>
>           <reportPlugins>
>             <plugin>
>               <groupId>org.apache.maven.plugins</groupId>
>               <artifactId>maven-changelog-plugin</artifactId>
>               <configuration>
>                 <issueIDRegexPattern>[A-Z]{2,}-\d+</issueIDRegexPattern>
>                 <issueLinkUrl>http://jira.example.co.uk</issueLinkUrl>
>                 <providerImplementations>
>                   <svn>javasvn</svn>
>                 </providerImplementations>
>               </configuration>
>             </plugin>
>           </reportPlugins>
>         </configuration>
>       </plugin>
>     </plugins>
>   </build>
>   
> </project>
> {noformat}

--
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-123) Patch with support for SCM provider implementations (similar to release plugin)

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

Olivier Lamy updated MCHANGELOG-123:
------------------------------------

    Fix Version/s: 2.3

> Patch with support for SCM provider implementations (similar to release plugin)
> -------------------------------------------------------------------------------
>
>                 Key: MCHANGELOG-123
>                 URL: https://jira.codehaus.org/browse/MCHANGELOG-123
>             Project: Maven 2.x Changelog Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Alex Coyle
>            Assignee: Olivier Lamy
>             Fix For: 2.3
>
>         Attachments: maven-changelog-plugin-scmproviderimpl.patch
>
>
> Hi,
> The attached patch includes support for SCM 'provider implementations', similar to what is included in the Maven Release Plugin. I made this change because I wanted to use the Changelog plugin with the maven-scm-provider-svnjava project (an SVN provider that uses SVNkit):
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
> I can confirm the patch works, and appears to generate a valid changelog report in the Maven site, when used with Maven 3.0.3 and a Maven project that follows this example POM structure:
> {noformat}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
>   
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>uk.co.example</groupId>
>   <artifactId>example-project</artifactId>
>   <packaging>pom</packaging>
>   <version>1.0.0-SNAPSHOT</version>
>   <name>Example Project</name>
>   <scm>
>     <url>http://example.co.uk/example-project</url>
>     <connection>scm:svn:http://svn.example.co.uk/example-project/trunk</connection>
>     <developerConnection>scm:svn:http://svn.example.co.uk/example-project/trunk</developerConnection>
>   </scm>
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-changelog-plugin</artifactId>
>         <version>2.3-SNAPSHOT</version>
>         <dependencies>
>           <dependency>
>             <groupId>com.google.code.maven-scm-provider-svnjava</groupId>
>             <artifactId>maven-scm-provider-svnjava</artifactId>
>             <version>1.13</version>
>           </dependency>
>         </dependencies>
>       </plugin>
>       <plugin>
>         <artifactId>maven-site-plugin</artifactId>
>         <version>3.0-beta-3</version>
>         <configuration>
>           <reportPlugins>
>             <plugin>
>               <groupId>org.apache.maven.plugins</groupId>
>               <artifactId>maven-changelog-plugin</artifactId>
>               <configuration>
>                 <issueIDRegexPattern>[A-Z]{2,}-\d+</issueIDRegexPattern>
>                 <issueLinkUrl>http://jira.example.co.uk</issueLinkUrl>
>                 <providerImplementations>
>                   <svn>javasvn</svn>
>                 </providerImplementations>
>               </configuration>
>             </plugin>
>           </reportPlugins>
>         </configuration>
>       </plugin>
>     </plugins>
>   </build>
>   
> </project>
> {noformat}

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