org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.5.1:deploy (default-deploy) on project parent-pom: Nexus connection problem to URL [http://cft-nexus.ldn.swissbank.com:8081/nexus/ ]: XPP3 pull parser library not present. Specify another driver. For example: new XStream(new DomDriver())

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 Peter Lynch, 1 year ago
Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.5.1:deploy (default-deploy) on project parent-pom: Nexus connection problem to URL [http://cft-nexus.ldn.swissbank.com:8081/nexus/ ]: XPP3 pull parser library not present. Specify another driver. For example: new XStream(new DomDriver())
via Sonatype JIRA by Peter Lynch, 1 year ago
Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.1:deploy (default) on project lucene: Execution default of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.1:deploy failed: Nexus connection problem to URL [https://localhost/nexus/service/local/staging/deploy/maven2/ ]: Cannot find a matching staging profile
via Sonatype JIRA by Ha Xiaolin, 5 months ago
Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.5.1:deploy (injected-nexus-deploy) on project galaxy-emq-client: Remote staging failed: 403 - Forbidden
via Sonatype JIRA by Peter Lynch, 1 year ago
Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.1:deploy-staged (default-cli) on project example-staging-m2: Execution default-cli of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.1:deploy-staged failed: BUG: finalizeDeploy invoked before deployPerModule?
via sonatype.org by Unknown author, 2 years ago
Failed to execute goal org.sonatype.plugins:nexus-m2settings-maven-plugin:1.5.2-SNAPSHOT:download (default-cli) on project nexus-maven-plugins: Connection failed
via Sonatype JIRA by Tamás Cservenák, 1 year ago
Failed to execute goal org.sonatype.plugins:nexus-m2settings-maven-plugin:1.5.1:download (default-cli) on project standalone-pom: Failed to save content to: C:\Users\xxx\.m2\settings.xml
java.lang.IllegalArgumentException: XPP3 pull parser library not present. Specify another driver. For example: new XStream(new DomDriver())
at org.sonatype.plexus.rest.xstream.xml.LookAheadXppDriver.loadLibrary(LookAheadXppDriver.java:66)
at org.sonatype.nexus.client.internal.rest.XStreamXmlProvider.readFrom(XStreamXmlProvider.java:84)
at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:565)
at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:517)
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:684)
at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
at org.sonatype.nexus.client.rest.jersey.JerseyNexusClient.getStatus(JerseyNexusClient.java:147)
at org.sonatype.nexus.client.internal.rest.AbstractNexusClient.initializeConnection(AbstractNexusClient.java:87)
at org.sonatype.nexus.client.rest.jersey.JerseyNexusClient.(JerseyNexusClient.java:91)
at org.sonatype.nexus.client.rest.jersey.NexusClientFactoryImpl.createFor(NexusClientFactoryImpl.java:110)
at org.sonatype.nexus.maven.staging.deploy.strategy.RemotingImpl.createNexusClient(RemotingImpl.java:221)
at org.sonatype.nexus.maven.staging.deploy.strategy.RemotingImpl.getNexusClient(RemotingImpl.java:139)
at org.sonatype.nexus.maven.staging.deploy.strategy.RemotingImpl.getStagingWorkflowV2Service(RemotingImpl.java:151)
at org.sonatype.nexus.maven.staging.deploy.strategy.AbstractStagingDeployStrategy.initRemoting(AbstractStagingDeployStrategy.java:97)
at org.sonatype.nexus.maven.staging.deploy.strategy.StagingDeployStrategy.deployPerModule(StagingDeployStrategy.java:70)
at org.sonatype.nexus.maven.staging.deploy.DeployMojo.execute(DeployMojo.java:193)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
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:317)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.