maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-855) Plugin does not support multiple SVN repositories
Date Wed, 13 Nov 2013 18:12:20 GMT

     [ https://jira.codehaus.org/browse/MRELEASE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte closed MRELEASE-855.
-----------------------------------

    Resolution: Duplicate
      Assignee: Robert Scholte
    
> Plugin does not support multiple SVN repositories
> -------------------------------------------------
>
>                 Key: MRELEASE-855
>                 URL: https://jira.codehaus.org/browse/MRELEASE-855
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.4.2
>            Reporter: Renato Del Gaudio
>            Assignee: Robert Scholte
>
> I have a multi modules project that uses several different repositories.
> e.g.
> Repository 1: https://hostname/svn/A
> Repository 2: https://hostname/svn/B
> Repository 3: https://hostname/svn/C
> Module A (Master build):  https://hostname/svn/A/moduleA
> Module B:  https://hostname/svn/B/moduleB
> Module C:  https://hostname/svn/C/moduleC
> IMPORTANT: 
> # Each module resided in its own repository with its own revision
> # Module B and C are children maven projects of module A
> Running *release:prepare* the plugin fails while trying to tag the repositories because
it tries to use the *same revision number* (the one from the last module) for all.
> The plugin is configured centrally in the parent pom in a paremetric way.
> The property software.id is the key that differentiate the repository within the *scm*
section that is the only part overwritten in the single child projects
> {code:xml} 
> <properties>
>   <software.id>A</software.id>
> </properties>
>   <scm> 
>    <connection>scm:svn:${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}</connection>
  	
>     <url>${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}</url>
  
>     <developerConnection>scm:svn:${scm.baseurl}/${software.id}/${scm.connection.version}/${project.artifactId}</developerConnection>
    
> </scm>
> <plugin> 
>         <groupId>org.apache.maven.plugins</groupId> 
>         <artifactId>maven-release-plugin</artifactId> 
>         <version>2.4</version> 
>         <configuration>
>           <commitByProject>true</commitByProject>
>           <useReleaseProfile>false</useReleaseProfile>
>           <preparationGoals>clean</preparationGoals> 
>           <tagNameFormat>MyProject_@{project.version}</tagNameFormat> 
>           <providerImplementations> 
>             <svn>javasvn</svn> 
>           </providerImplementations> 
>         </configuration> 
>         <dependencies> 
>           <dependency>
>                 <groupId>com.google.code.maven-scm-provider-svnjava</groupId>
>                 <artifactId>maven-scm-provider-svnjava</artifactId>
>                 <version>2.0.5</version>
>             </dependency>
>             <dependency>
>                 <groupId>org.tmatesoft.svnkit</groupId>
>                 <artifactId>svnkit</artifactId>
>                 <version>1.7.6</version>
>             </dependency>
>             <dependency>
>                 <groupId>org.apache.maven.plugins</groupId>
>                 <artifactId>maven-scm-plugin</artifactId>
>                 <version>1.8.1</version>
>             </dependency>
>         </dependencies> 
>       </plugin>
> {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