[
http://jira.codehaus.org/browse/SCM-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139110#action_139110
]
Mark Struberg commented on SCM-182:
-----------------------------------
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:
{noformat}
<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>
{noformat}
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.
> git provider
> ------------
>
> Key: SCM-182
> URL: http://jira.codehaus.org/browse/SCM-182
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-scm-provider-git
> Environment: Developed on Mac OS X 10.3.9 with git 1.2.4
> Reporter: Dominik Winter
> Assignee: Jason van Zyl
> Fix For: 1.1
>
> Attachments: git.patch, git.tar.bz2, SCM-182.patch, update1.patch.bz2
>
>
> Please find the git provider as attachment.
> Usefulness:
> I used the git provider together with
> [http://maven.apache.org/plugins/maven-release-plugin|maven-release-plugin],
> it works fine for that use case.
> Open issues:
> - the JUnit tests are "proprietary", not yet TCK. I'll fix that.
> If you want to run the tests, you must have git installed and it must be in
> your {{PATH}}.
> To run git:
> - on *Windows*: use [Cygwin|http://www.cygwin.com] and install the binutils,
> openssh, openssl, rsync, curl
> than you are able to compile and install git
> - on Linux: there are packages somewhere
> - on Mac OS X: use the [DarwinPorts|http://www.darwinports.org/]
--
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
