[jira] [Commented] (MRELEASE-911) release plugin forming incorrect git clone command

2017-08-04 Thread Med Reda (JIRA)

[ 
https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114323#comment-16114323
 ] 

Med Reda commented on MRELEASE-911:
---

yes but dosn't work for me so i  use release:prepare release:perform and i use 
a script to create Release branche from a created tag.
thanks


> release plugin forming incorrect git clone command
> --
>
> Key: MRELEASE-911
> URL: https://issues.apache.org/jira/browse/MRELEASE-911
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: Git
>Affects Versions: 2.5.2
>Reporter: sandyzden
>
> git-exe plugin completely ignores the branch parameter and fails in cloning 
> the repository during {{release:perform}}
> e.g. git clone --branch   this causes it to determine 
> the  as the branch parameter and failing.
> Below is the error message
> {noformat}
> [ERROR] The git-clone command failed.
> [ERROR] fatal: repository '/target/checkout' does not exist
> {noformat}
> A bit fiddling on the source code i found out 
> {code}
>  if ( version != null && ( version instanceof ScmBranch ) )
> {
> cl.createArg().setValue( "--branch" );
> cl.createArg().setValue( version.getName() );
> }
> {code}
> it needed version number, but i was not able to figure how it passed from 
> Main Mojo to this class



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MRELEASE-911) release plugin forming incorrect git clone command

2017-08-01 Thread Robert Scholte (JIRA)

[ 
https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109293#comment-16109293
 ] 

Robert Scholte commented on MRELEASE-911:
-

[~inforedaster] have you read 
http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html 
?

> release plugin forming incorrect git clone command
> --
>
> Key: MRELEASE-911
> URL: https://issues.apache.org/jira/browse/MRELEASE-911
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: Git
>Affects Versions: 2.5.2
>Reporter: sandyzden
>
> git-exe plugin completely ignores the branch parameter and fails in cloning 
> the repository during {{release:perform}}
> e.g. git clone --branch   this causes it to determine 
> the  as the branch parameter and failing.
> Below is the error message
> {noformat}
> [ERROR] The git-clone command failed.
> [ERROR] fatal: repository '/target/checkout' does not exist
> {noformat}
> A bit fiddling on the source code i found out 
> {code}
>  if ( version != null && ( version instanceof ScmBranch ) )
> {
> cl.createArg().setValue( "--branch" );
> cl.createArg().setValue( version.getName() );
> }
> {code}
> it needed version number, but i was not able to figure how it passed from 
> Main Mojo to this class



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MRELEASE-911) release plugin forming incorrect git clone command

2017-08-01 Thread Med Reda (JIRA)

[ 
https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108570#comment-16108570
 ] 

Med Reda commented on MRELEASE-911:
---

release:prepare  + release:perform ==> create a tag has version without snapshot
release:branch ==> create branche has version with -SNAPSHOT

when i add release:branch + release:perform i have this problem :

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on 
project impulse-sdk: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] fatal: repository 
'/home/jenkins/workspace/release-exp/reda-projects/target/checkout' does not 
exist

how can i have release:branch  + release:perform ==> create a branch has 
version without snapshot ??!!

any help please

> release plugin forming incorrect git clone command
> --
>
> Key: MRELEASE-911
> URL: https://issues.apache.org/jira/browse/MRELEASE-911
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: Git
>Affects Versions: 2.5.2
>Reporter: sandyzden
>
> git-exe plugin completely ignores the branch parameter and fails in cloning 
> the repository during {{release:perform}}
> e.g. git clone --branch   this causes it to determine 
> the  as the branch parameter and failing.
> Below is the error message
> {noformat}
> [ERROR] The git-clone command failed.
> [ERROR] fatal: repository '/target/checkout' does not exist
> {noformat}
> A bit fiddling on the source code i found out 
> {code}
>  if ( version != null && ( version instanceof ScmBranch ) )
> {
> cl.createArg().setValue( "--branch" );
> cl.createArg().setValue( version.getName() );
> }
> {code}
> it needed version number, but i was not able to figure how it passed from 
> Main Mojo to this class



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MRELEASE-911) release plugin forming incorrect git clone command

2017-07-31 Thread Med Reda (JIRA)

[ 
https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107376#comment-16107376
 ] 

Med Reda commented on MRELEASE-911:
---

When i use release:prepare with release:perform it works fin and it creates a 
tag otherwise i need a branch instead of tag with this command i have the same 
issue :

mvn clean -DreleaseVersion=${v} -DdevelopmentVersion=${newdevversion} 
-DpreparationGoals=clean verify release:branch -DbranchName=release-${v} 
release:perform 
-DconnectionUrl=scm:git:g...@git.project.net:project-domaine/poc/reda-projects.git
 -B

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on 
project impulse-sdk: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] fatal: repository 
'/home/jenkins/workspace/release-exp/reda-projects/target/checkout' does not 
exist

When i check the existing directory : 
'/home/jenkins/workspace/release-exp/reda-projects/target but not have a 
"checkout" directory.
any idea ?


> release plugin forming incorrect git clone command
> --
>
> Key: MRELEASE-911
> URL: https://issues.apache.org/jira/browse/MRELEASE-911
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: Git
>Affects Versions: 2.5.2
>Reporter: sandyzden
>
> git-exe plugin completely ignores the branch parameter and fails in cloning 
> the repository during {{release:perform}}
> e.g. git clone --branch   this causes it to determine 
> the  as the branch parameter and failing.
> Below is the error message
> {noformat}
> [ERROR] The git-clone command failed.
> [ERROR] fatal: repository '/target/checkout' does not exist
> {noformat}
> A bit fiddling on the source code i found out 
> {code}
>  if ( version != null && ( version instanceof ScmBranch ) )
> {
> cl.createArg().setValue( "--branch" );
> cl.createArg().setValue( version.getName() );
> }
> {code}
> it needed version number, but i was not able to figure how it passed from 
> Main Mojo to this class



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (MRELEASE-911) release plugin forming incorrect git clone command

2015-05-19 Thread sandyzden (JIRA)

[ 
https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551862#comment-14551862
 ] 

sandyzden commented on MRELEASE-911:


[~rfscholte]

i am not calling release:branch, but rather using release:perform which during 
checkout to local target/checkout directory is causing the issue.

 release plugin forming incorrect git clone command
 --

 Key: MRELEASE-911
 URL: https://issues.apache.org/jira/browse/MRELEASE-911
 Project: Maven Release Plugin
  Issue Type: Bug
  Components: Git
Affects Versions: 2.5.2
Reporter: sandyzden

 git-exe plugin completely ignores the branch parameter and fails in cloning 
 the repository during {{release:perform}}
 e.g. git clone --branch git url working dir this causes it to determine 
 the working dir as the branch parameter and failing.
 Below is the error message
 {noformat}
 [ERROR] The git-clone command failed.
 [ERROR] fatal: repository 'working dir/target/checkout' does not exist
 {noformat}
 A bit fiddling on the source code i found out 
 {code}
  if ( version != null  ( version instanceof ScmBranch ) )
 {
 cl.createArg().setValue( --branch );
 cl.createArg().setValue( version.getName() );
 }
 {code}
 it needed version number, but i was not able to figure how it passed from 
 Main Mojo to this class



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MRELEASE-911) release plugin forming incorrect git clone command

2015-05-14 Thread Robert Scholte (JIRA)

[ 
https://issues.apache.org/jira/browse/MRELEASE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14544338#comment-14544338
 ] 

Robert Scholte commented on MRELEASE-911:
-

{{release:perform}} has nothing to do with branches. It checks out a _tag_ 
created by {{release:prepare}} and calls {{mvn deploy}} on the checked out 
directory.
What are you trying to do? {{release:branch}} followed by {{release:perform}}?

 release plugin forming incorrect git clone command
 --

 Key: MRELEASE-911
 URL: https://issues.apache.org/jira/browse/MRELEASE-911
 Project: Maven Release Plugin
  Issue Type: Bug
  Components: Git
Affects Versions: 2.5.2
Reporter: sandyzden

 git-exe plugin completely ignores the branch parameter and fails in cloning 
 the repository during {{release:perform}}
 e.g. git clone --branch git url working dir this causes it to determine 
 the working dir as the branch parameter and failing.
 Below is the error message
 {noformat}
 [ERROR] The git-clone command failed.
 [ERROR] fatal: repository 'working dir/target/checkout' does not exist
 {noformat}
 A bit fiddling on the source code i found out 
 {code}
  if ( version != null  ( version instanceof ScmBranch ) )
 {
 cl.createArg().setValue( --branch );
 cl.createArg().setValue( version.getName() );
 }
 {code}
 it needed version number, but i was not able to figure how it passed from 
 Main Mojo to this class



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)