Hi, I have cleaned my repo and try it again. I always have the same issue. I have try with this with cli : mvn stage:copy -Dsource="http://people.apache.org/~olamy/staging-repo/"; -Dtarget="scp://people.apache.org/home/olamy/tmp" -Dversion=2.0.8 -DtargetRepositoryId=apache.releases
Can someone else try with a different target -Dtarget="scp://people.apache.org/home/YOUR_APACHE_USER_NAME/tmp" Note at the end, there a file staging-plugin-2.0.8.zip in the remote target. -- Olivier 2008/5/19 Brett Porter <[EMAIL PROTECTED]>: > I also used the final RC of 2.0.9 to release Archiva last time. > > I did change the filtering for wagon-ssh in a much earlier commit - that > would be my initial guess, but I also have a feeling I would have tried > stage copying with that in place already. > > Is this being done with the latest release of the stage plugin, or trunk? > > - Brett > > On 18/05/2008, at 4:50 AM, Brian E. Fox wrote: > >> That's weird. I used 2.0.9 to stage and release 2.0.9 >> >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of >> Olivier Lamy >> Sent: Saturday, May 17, 2008 10:12 AM >> To: Maven Developers List >> Subject: stage:copy ClassCastException with maven 2.0.9 >> >> Hi, >> I have just try to stage the maven-invoker and I have the following >> exception : >> >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] org.apache.maven.wagon.providers.ssh.jsch.ScpWagon >> [INFO] >> ------------------------------------------------------------------------ >> [DEBUG] Trace >> java.lang.ClassCastException: >> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon >> at >> org.apache.maven.plugins.stage.DefaultRepositoryCopier.copy(DefaultRepos >> itoryCopier.java:252) >> at >> org.apache.maven.plugins.stage.CopyRepositoryMojo.execute(CopyRepository >> Mojo.java:93) >> 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.executeStandaloneGoa >> l(DefaultLifecycleExecuto >> >> The workaround was to use maven 2.0.8. >> >> -- >> Olivier >> >> --------------------------------------------------------------------- >> 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] >> > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > > > --------------------------------------------------------------------- > 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]
