Re: Can no longer deploy project artifacts using maven3

2011-04-06 Thread Marc Rohlfs
Tim, I hope You don't mind the question, but did You add the the wagon jar to the MAVEN_HOME/lib directory on Your Hudson server, too? Anyway, I'd rather not add any libraries to the MAVEN_HOME/lib directory, because this needs to be done on each and every server and workstation where the

Re: Can no longer deploy project artifacts using maven3

2011-04-06 Thread Tim Pizey
Hi Marc, On 6 April 2011 09:52, Marc Rohlfs wrote: Tim, I hope You don't mind the question, but did You add the the wagon jar to the MAVEN_HOME/lib directory on Your Hudson server, too? Thanks, no, I had not. I have now, and it still does not work:

Re: Can no longer deploy project artifacts using maven3

2011-04-06 Thread Tim Pizey
Hi, I now have my project deploying using scp. I added an explicit configuration for the deploy plugin to the pom: plugin artifactIdmaven-deploy-plugin/artifactId version2.5/version dependencies dependency groupIdorg.apache.maven.wagon/groupId

Re: Can no longer deploy project artifacts using maven3

2011-04-06 Thread Marc Rohlfs
Hi Tim, On 06/04/11 12:34, Tim Pizey wrote: I cannot see in what sense ssh is an extension ... In the sense that it is not incuded in the Maven core anymore ... ;) ... But if You really need different configurations for M2 and M3, You could use different profiles that are automatically

Re: Can no longer deploy project artifacts using maven3

2011-04-06 Thread Jason van Zyl
If this is for a Sourceforge (I saw Webmacro in there) project then the route that many have gone is to drop SCP, and use Nexus OSS. There are 1300 projects using Nexus OSS now, it's easier to get your project into Maven Central and you don't have to worry about the Maven repository

Re: Can no longer deploy project artifacts using maven3

2011-04-06 Thread Tim Pizey
Hi Jason, Marc, Thankyou for your help. I am now back to working for M2 and M3, but it looks like I need to get with the plot and use Nexus. I have never understood why the maven generated site does not link to the default distribution repo., nor why the decision was taken not to persue per

Re: Can no longer deploy project artifacts using maven3

2011-04-06 Thread Jason van Zyl
On Apr 6, 2011, at 8:33 AM, Tim Pizey wrote: Hi Jason, Marc, Thankyou for your help. I am now back to working for M2 and M3, but it looks like I need to get with the plot and use Nexus. I have never understood why the maven generated site does not link to the default distribution

Re: Can no longer deploy project artifacts using maven3

2011-04-06 Thread Tim Pizey
Hi Jason, thank you for your detailed reply. On 6 April 2011 13:59, Jason van Zyl wrote: On Apr 6, 2011, at 8:33 AM, Tim Pizey wrote: Hi Jason, Marc, Thankyou for your help. I am now back to working for M2 and M3, but it looks like I need to get with the plot and use Nexus. I have

Can no longer deploy project artifacts using maven3

2011-04-05 Thread Tim Pizey
Hi, I have tried to update my project to use maven3 (version 3.0.2), however I can no longer deploy artifacts to my repository. I have found a number of notes about how to do this: https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html Gives Transport Protocols (Wagons) Unlike

Re: Can no longer deploy project artifacts using maven3

2011-04-05 Thread John Casey
Try turning that extension into a dependency embedded in the maven-deploy-plugin configuration, IIRC: build plugins plugin artifactIdmaven-deploy-plugin/artifactId version2.5/version dependencies dependency groupIdorg.apache.maven.wagon/groupId

Re: Can no longer deploy project artifacts using maven3

2011-04-05 Thread Tim Pizey
John, Thank you very much for the reply. I have two setups, local and on a CI server, which is still running maven2. This did not work under maven2 on the CI server: http://jenkins.paneris.net/job/melati/134/console but I will try at work tomorrow under maven3. I guess not that many people