[
https://issues.apache.org/jira/browse/MRELEASE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531079#comment-17531079
]
Vilius Šumskas commented on MRELEASE-839:
-----------------------------------------
I can do tests if needed however I'm not Java developer so I'm unable to
provide PR. The main issue here is that since changes in MRELEASE-796 arguments
to git is passed incorrectly.
*Tests I performed*
This works without errors:
{code:java}
mvn org.apache.maven.plugins:maven-release-plugin:2.2.2:perform
-DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git
-Dtag=0.1.14 -DuseReleaseProfile=false{code}
{code:java}
[INFO] Executing: cmd.exe /X /C "git clone
https://gitlab.com/fake/r365-autoconfig.git
C:\temp1\r365-autoconfig\target\checkout"
[INFO] Executing: cmd.exe /X /C "git ls-remote
https://gitlab.com/fake/r365-autoconfig.git";
[INFO] Executing: cmd.exe /X /C "git fetch
https://gitlab.com/fake/r365-autoconfig.git";
[INFO] Executing: cmd.exe /X /C "git checkout 0.1.14"
...build starts
{code}
however you cannot use it -DlocalCheckout=true:
{code:java}
mvn org.apache.maven.plugins:maven-release-plugin:2.2.2:perform
-DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git
-Dtag=0.1.14 -DuseReleaseProfile=false -DlocalCheckout=true{code}
{code:java}
[INFO] Executing: cmd.exe /X /C "git clone file://C\temp1\r365-autoconfig
C:\temp1\r365-autoconfig\target\checkout"
[INFO] Working directory: C:\temp1\r365-autoconfig\target
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on
project r365-autoconfig: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] Cloning into 'C:\temp1\r365-autoconfig\target\checkout'...
[ERROR] fatal: '/C/temp1/r365-autoconfig' does not appear to be a git
repository{code}
With 2.3.2 it works, and this time you can use it with localCheckout too:
{code:java}
mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:perform
-DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git
-Dtag=0.1.14 -DuseReleaseProfile=false{code}
{code:java}
[INFO] Executing: cmd.exe /X /C "git clone --branch 0.1.14
https://gitlab.com/fake/r365-autoconfig.git
C:\temp1\r365-autoconfig\target\checkout"
[INFO] Executing: cmd.exe /X /C "git ls-remote
https://gitlab.com/fake/r365-autoconfig.git";
[INFO] Executing: cmd.exe /X /C "git fetch
https://gitlab.com/fake/r365-autoconfig.git";
[INFO] Executing: cmd.exe /X /C "git checkout 0.1.14"
...build starts{code}
{code:java}
mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:perform
-DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git
-Dtag=0.1.14 -DuseReleaseProfile=false -DlocalCheckout=true{code}
{code:java}
[INFO] Executing: cmd.exe /X /C "git clone --branch 0.1.14
file:///C:\temp1\r365-autoconfig C:\temp1\r365-autoconfig\target\checkout"
[INFO] Executing: cmd.exe /X /C "git ls-remote file:///C:\temp1\r365-autoconfig"
[INFO] Executing: cmd.exe /X /C "git fetch file:///C:\temp1\r365-autoconfig"
[INFO] Executing: cmd.exe /X /C "git checkout 0.1.14"
..build starts{code}
Anything above 2.3.2 produces errors with or without localCheckout:
{code:java}
mvn org.apache.maven.plugins:maven-release-plugin:2.5.2:perform
-DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git
-Dtag=0.1.14 -DuseReleaseProfile=false{code}
{code:java}
[INFO] Executing: cmd.exe /X /C "git clone --branch
https://gitlab.com/fake/r365-autoconfig.git
C:\temp1\r365-autoconfig\target\checkout"
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.2:perform (default-cli) on
project r365-autoconfig: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] Cloning into 'checkout'...
[ERROR] fatal: Remote branch https://gitlab.com/fake/r365-autoconfig.git not
found in upstream origin{code}
{code:java}
mvn org.apache.maven.plugins:maven-release-plugin:3.0.0-M5:perform
-DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git
-Dtag=0.1.14 -DuseReleaseProfile=false{code}
{code:java}
[INFO] Executing: cmd.exe /X /C "git clone --depth 1 --branch
https://gitlab.com/fake/r365-autoconfig.git checkout"
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:3.0.0-M5:perform (default-cli) on
project r365-autoconfig: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] fatal: repository 'checkout' does not exist{code}
> Unable to supply tag to release for release:perform
> ---------------------------------------------------
>
> Key: MRELEASE-839
> URL: https://issues.apache.org/jira/browse/MRELEASE-839
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.4.1
> Reporter: Tuure Laurinolli
> Priority: Major
>
> The documentation at
> http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html
> and
> http://maven.apache.org/maven-release/maven-release-plugin/plugin-info.html
> claims that releases can be ma de of a specific tag, but no mechanism for
> this is specified.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
