Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Sonatype JIRA by Florian Brunner, 1 year ago
Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.1:prepare (default-cli) on project softsmithy-parent: Unable to commit files Provider message: EXECUTION FAILED Execution of cmd : push failed with exit code: 255. Working
via Google Groups by Luís António, 2 years ago
Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project gam-core: Unable to commit files Provider message: The git-push command failed. Command output: ssh: connect to host gitserver.com port 22: Connection refused fatal: The remote end hung up unexpectedly
via Stack Overflow by user2657065
, 2 years ago
Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.1:perform (default-cli) on project logreport: Maven execution failed, exit code: '1'
via Google Groups by dredd, 2 years ago
Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:perform (default-cli) on project utils: Maven execution failed, exit code: '1'
via Stack Overflow by Andrey
, 2 years ago
Failed to execute goal org.codehaus.sonar:sonar-maven3-plugin:3.3.1:sonar (default-cli) on project proj-parent: Execution default-cli of goal org.codehaus.sonar:sonar-maven3-plugin:3.3.1:sonar failed: null value
via Google Groups by Frédéric Bouquet, 2 years ago
Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare (default-cli) on project test-release-plugin: An error is occurred in the checkin process: Exception while executing SCM command.
org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to commit files
Provider message:
EXECUTION FAILED
  Execution of cmd : push failed with exit code: 255.
  Working directory was: 
    /var/lib/jenkins/jobs/SoftSmithy-Parent-Release/workspace
  Your Hg installation seems to be valid and complete.
    Hg version: 2.2.3 (OK)
Command output:	at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:168)	at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:148)	at org.apache.maven.shared.release.phase.ScmCommitDevelopmentPhase.runLogic(ScmCommitDevelopmentPhase.java:89)	at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.execute(AbstractScmCommitPhase.java:79)	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:279)	at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:237)	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)	at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)	at java.lang.reflect.Method.invoke(Method.java:601)	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)	at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)	at hudson.maven.Maven3Builder.call(Maven3Builder.java:98)	at hudson.maven.Maven3Builder.call(Maven3Builder.java:64)	at hudson.remoting.UserRequest.perform(UserRequest.java:118)	at hudson.remoting.UserRequest.perform(UserRequest.java:48)	at hudson.remoting.Request$2.run(Request.java:326)	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)	at java.util.concurrent.FutureTask.run(FutureTask.java:166)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)	at java.lang.Thread.run(Thread.java:722)