maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Dahanne (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (SCM-556) Vague error message from git-scm-plugin prevents release:prepare
Date Mon, 20 Sep 2010 01:25:32 GMT

    [ http://jira.codehaus.org/browse/SCM-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235775#action_235775
] 

Anthony Dahanne commented on SCM-556:
-------------------------------------

@Roberto Tyley : I had exactly the same problem as you; and removing the release.properties
and putting back my pom version to a SNAPSHOT (it was previously changed by the plugin) version
resolved the problem; the process ended successfully.
Hope it helps !

> Vague error message from git-scm-plugin prevents release:prepare
> ----------------------------------------------------------------
>
>                 Key: SCM-556
>                 URL: http://jira.codehaus.org/browse/SCM-556
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-git
>    Affects Versions: 1.3
>            Reporter: Paul Hammant
>
> "Unable to commit files" is vague I think.
> The only special thing I'm trying to do is commit from a branch that is not master. 
Yes, the branch has remote representation (fully pushed) as well as local.
> For the record the project is paranamer on codehaus, which was flipped from Subversion
to Git. http://xircles.codehaus.org/projects/paranamer/repo/git/repo  .... real_asm branch.
> -e -X console output :
> [DEBUG] # On branch real_asm
> [DEBUG] # Untracked files:
> [DEBUG] #   (use "git add <file>..." to include in what will be committed)
> [DEBUG] #
> [DEBUG] #	pom.xml.releaseBackup
> [DEBUG] #	release.properties
> [DEBUG] nothing added to commit but untracked files present (use "git add" to track)
> [INFO] nothing added to commit but untracked files present (use "git add" to track)
> [INFO] Executing: /bin/sh -c cd /scm/oss/paranamer-git/paranamer && git commit
--verbose -F /var/folders/qb/qbAjORvlEIKOmBNFQArSs++++TI/-Tmp-/maven-scm-890989155.commit
pom.xml
> [INFO] Working directory: /scm/oss/paranamer-git/paranamer
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The git-commit command failed.
> Command output:
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Unable to commit files
> Provider message:
> The git-commit command failed.
> Command output:
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> 	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> 	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> 	at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> 	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> 	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> 	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files
> Provider message:
> The git-commit command failed.
> Command output:
> 	at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219)
> 	at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181)
> 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> 	... 17 more
> Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to
commit files
> Provider message:
> The git-commit command failed.
> Command output:
> 	at org.apache.maven.shared.release.phase.ScmCommitPhase.checkin(ScmCommitPhase.java:133)
> 	at org.apache.maven.shared.release.phase.ScmCommitPhase.execute(ScmCommitPhase.java:109)
> 	at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203)
> 	at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
> 	at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
> 	at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
> 	... 20 more
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 55 seconds
> [INFO] Finished at: Thu Jun 10 05:35:32 CDT 2010
> [INFO] Final Memory: 26M/79M

-- 
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

        

Mime
View raw message