Those wagons are not compatible with maven 2.0.9 or less. -----Original Message----- From: Chris Lieb [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2008 12:10 PM To: users@maven.apache.org Subject: Re: Apparent Plugin Version Mismatch with maven-deploy-plugin and wagon-ftp
I was accidentally overriding the versions that were set in the master POM in the project that I was testing in. After I fixed that, the deploy phase started working again. Is there a reason why 1.0-beta-3 of wagon-ftp and wagon-provider-api don't seem to work? Chris Lieb Chris Lieb wrote: > I have a project that deploys using the wagon-ftp plugin. It has been > building without issue for months now through CruiseControl. Over the > weekend when a build was triggered, it failed when it tried to deploy > the project's POM, the first item that is deployed in the build > process. I get the following error message: > > > [INFO] Retrieving previous build number from inhouse_snapshot > [FATAL ERROR] org.apache.maven.plugin.deploy.DeployMojo#execute() > caused a linkage error (java.lang.AbstractMethodError) and may be > out-of-date. Check the realms: > [FATAL ERROR] Plugin realm = > app0.child-container[org.apache.maven.plugins:maven-deploy-plugin] > urls[0] = file:/C:/Documents and > Settings/Administrator/.m2/repository/org/apache/maven/plugins/maven-dep loy-plugin/2.3/maven-deploy-plugin-2.3.jar > > urls[1] = file:/C:/Documents and > Settings/Administrator/.m2/repository/org/codehaus/plexus/plexus-utils/1 .1/plexus-utils-1.1.jar > > [FATAL ERROR] Container realm = plexus.core > urls[0] = file:/C:/Program Files/Apache Software > Foundation/maven-2.0/bin/../lib/maven-2.0.9-uber.jar > [INFO] > ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection()V > [INFO] > ------------------------------------------------------------------------ > [DEBUG] Trace > java.lang.AbstractMethodError: > org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection()V > at > org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(Defa ultWagonManager.java:435) > > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadat aFromDeploymentRepository(DefaultWagonManager.java:379) > > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataM anager.getArtifactMetadataFromDeploymentRepository(DefaultRepositoryMeta dataManager.java:380) > > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataM anager.resolveAlways(DefaultRepositoryMetadataManager.java:348) > > at > org.apache.maven.artifact.transform.SnapshotTransformation.resolveLatest SnapshotBuildNumber(SnapshotTransformation.java:161) > > at > org.apache.maven.artifact.transform.SnapshotTransformation.transformForD eployment(SnapshotTransformation.java:100) > > at > org.apache.maven.artifact.transform.DefaultArtifactTransformationManager .transformForDeployment(DefaultArtifactTransformationManager.java:78) > > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul tArtifactDeployer.java:71) > > at > org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:152) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:451) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:558) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:499) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:478) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:330) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:291) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:142) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:585) > 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) > > I have tried forcing the version numbers on wagon-ftp and > wagon-provider-api to 1.0-beta-2 since I think that the newer > 1.0-beta-3 was pulled down last week, but I still get the same error. > > Does anyone have any idea what is causing this? > > Thanks, > Chris Lieb --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
