jira-importer commented on issue #386:
URL: https://github.com/apache/maven-scm/issues/386#issuecomment-2964591058

   **[Mark 
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
 commented
   
   The full way to get it up and running is a bit complicated, since if you 
like to use the git provider for releasing, no snapshot has to be in your pom.
   
   You could either build the whole maven2 project from source, or only the scm 
parts.
   
   Probably the most easiest way is to make a 'private' release of the whole 
maven-scm-plugin (I used the extension 'msx-1') and the maven-release-plugin. 
It is important that those versions are no SNAPSHOTS (otherwise the release 
will fail). Then use it as:
   
   ```
   <plugins>
     <plugin>
       <groupId>org.apache.maven.plugins</groupId>
       <artifactId>maven-scm-plugin</artifactId>
       <version>1.1-msx-1</version>
       <dependencies>
         <dependency>
           <groupId>org.apache.maven.scm</groupId>
           <artifactId>maven-scm-provider-gitexe</artifactId>
           <version>1.1-msx-1</version>
         </dependency>
       </dependencies>
     </plugin>
     <plugin>
       <groupId>org.apache.maven.plugins</groupId>
       <artifactId>maven-release-plugin</artifactId>
       <version>2.0-beta-8-msx-1</version>
       <dependencies>
         <dependency>
           <groupId>org.apache.maven.plugins</groupId>
           <artifactId>maven-scm-plugin</artifactId>
           <version>1.1-msx-1</version>
         </dependency>
         <dependency>
           <groupId>org.apache.maven.scm</groupId>
           <artifactId>maven-scm-api</artifactId>
           <version>1.1-msx-1</version>
         </dependency>          
       </dependencies>
     </plugin>
   </plugins>
   ```
   
   This is mainly a workaround for testing the scm provider with released maven 
versions (I tested with 2.0.4, 2.0.8 and SNAPSHOT)
   And we will get rid of all this pain if 1.1 is finally released soon.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to