org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error retrieving previous build number for artifact '$PROJECT:$SUBPROJECT:pom': repository metadata for: 'snapshot $PROJECT:$SUBPROJECT:$VERSION-SNAPSHOT' could not be retrieved from repository: $M2_REPO due to an error: While configuring wagon for '$M2_REPO': Unable to apply wagon configuration.

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 Jenkins JIRA by Costin Caraivan, 1 year ago
Error retrieving previous build number for artifact '$PROJECT:$SUBPROJECT:pom': repository metadata for: 'snapshot $PROJECT:$SUBPROJECT:$VERSION-SNAPSHOT' could not be retrieved from repository: $M2_REPO due to an error: While configuring wagon for '$M2_REPO': Unable to apply wagon configuration.
via Google Groups by Jorg Heymans, 2 years ago
Error retrieving previous build number for artifact 'my.group:artifact:jar': Cannot read metadata from '/home/ci/.m2/repository/my/group/artifact/0.2-SNAPSHOT/maven-metadata-agri-snapshot.xml': expected START_TAG or END_TAG not TEXT (position: TEXT seen ...<extension>jar</... @14:25)
via archiva-users by EJ Ciramella, 1 year ago
Error retrieving previous build number for artifact 'com.upromise.atgModule:olmAtgCommon:atg-module': reposito ry metadata for: 'snapshot com.upromise.atgModule:olmAtgCommon:2009-P2008006-SNAPSHOT' could not be retrieved from repository: bertha due to an error: Error transferring file
via Atlassian JIRA by James Roper [Atlassian], 1 year ago
Error retrieving previous build number for artifact 'com.atlassian.bamboo:atlassian-bamboo:pom': repository metadata for: 'snapshot com.atlassian.bamboo:atlassian-bamboo:2.4-SNAPSHOT' could not be retrieved from repository: atlassian-private-snapshot due to an error: Connection failed: Connection Exception: wrong class use
via Sonatype JIRA by Maciek Makowski, 1 year ago
Error retrieving previous build number for artifact 'com.mmakowski:maven-specs2-plugin:maven-plugin': repository metadata for: 'snapshot com.mmakowski:maven-specs2-plugin:0.3.0-SNAPSHOT' could not be retrieved from repository: oss.sonatype.org due
via Sonatype JIRA by Maciek Makowski, 1 year ago
Error retrieving previous build number for artifact 'com.mmakowski:maven-specs2-plugin:maven-plugin': repository metadata for: 'snapshot com.mmakowski:maven-specs2-plugin:0.3.0-SNAPSHOT' could not be retrieved from repository: oss.sonatype.org due
org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error retrieving previous build number for artifact '$PROJECT:$SUBPROJECT:pom': repository metadata for: 'snapshot $PROJECT:$SUBPROJECT:$VERSION-SNAPSHOT' could not be retrieved from repository: $M2_REPO due to an error: While configuring wagon for '$M2_REPO': Unable to apply wagon configuration.
at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.(ComponentValueSetter.java:68)
at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134)
at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
at org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent(AbstractComponentConfigurator.java:54)
at org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(DefaultWagonManager.java:993)
at org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(DefaultWagonManager.java:980)
at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:400)
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadataFromDeploymentRepository(DefaultWagonManager.java:379)
at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.getArtifactMetadataFromDeploymentRepository(DefaultRepositoryMetadataManager.java:380)
at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:348)
at org.apache.maven.artifact.transform.SnapshotTransformation.resolveLatestSnapshotBuildNumber(SnapshotTransformation.java:161)
at org.apache.maven.artifact.transform.SnapshotTransformation.transformForDeployment(SnapshotTransformation.java:100)
at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForDeployment(DefaultArtifactTransformationManager.java:78)
at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:119)
at hudson.maven.reporters.MavenAggregatedArtifactRecord.deploy(MavenAggregatedArtifactRecord.java:79)
at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:96)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:480)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:590)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:438)
at hudson.model.Run.run(Run.java:1140)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:300)
at hudson.model.ResourceController.execute(ResourceController.java:93)
at hudson.model.Executor.run(Executor.java:122)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

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