Possible, but I checked the ${M2_HOME}/conf/settings.xml and the
repositories have valid username/passwords on the associated servers.Credentials for scp wouldn't be resolved differently from within the release plugin, would they? FWIW, I've reverted from 2.1.0 back to 2.0.8 and get the same behavior. [The settings.xml files are identical for both versions. Most oddly, though, I've noticed that the deploymentRepository shown in the mojo configuration [below] isn't a valid URL. It's one that's been deprecated for several months. There's apparently some settings cruft hanging around, but I'm stumped. Brad -----Original Message----- From: Brian Fox [mailto:bri...@infinity.nu] Sent: Thursday, May 07, 2009 5:20 PM To: Maven Users List Subject: Re: deploy:deploy Hangs in Release I wonder if it's waiting for some password input. Make sure you have a server setting with the proper credentials for scp. On Tue, May 5, 2009 at 6:33 PM, Harper, Brad <brad.har...@fiserv.com> wrote: > While performing a deployment from the release plugin, I see > > > > [INFO] [INFO] [install:install] > > [INFO] [INFO] Installing C:\eclipse-workspaces\...\x.war to > C:\...\.m2\repository\com\...\x.war > > [INFO] [INFO] Installing C:\eclipse-workspaces\...\x-sources.jar to > C:\...\.m2\repository\com\x-sources.jar > > [INFO] [INFO] Installing C:\eclipse-workspaces\...\x.zip to C:\...\x.zip > > [INFO] [INFO] [deploy:deploy] > > > > And that's it. Re-running with -X gives > > > > . . . > > [INFO] [DEBUG] Configuring mojo > 'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' --> > > [INFO] [DEBUG] (f) artifact = x:war:1.0.4 > > [INFO] [DEBUG] (f) attachedArtifacts = > [com.y:x:java-source:sources:1.0.4, com.y:x:zip:1.0.4] > > [INFO] [DEBUG] (f) deploymentRepository = > Repository[internal|scp://dev-deploy/web-dev-repos/releases] > > [INFO] [DEBUG] (s) localRepository = > Repository[local|file://C:\...\.m2\repository] > > [INFO] [DEBUG] (f) packaging = war > > [INFO] [DEBUG] (f) pomFile = > C:\eclipse-workspaces\...\x\target\checkout\pom.xml > > [INFO] [DEBUG] (f) skip = false > > [INFO] [DEBUG] (f) updateReleaseInfo = true > > [INFO] [DEBUG] -- end configuration -- > > [INFO] [INFO] [deploy:deploy] > > [INFO] [DEBUG] not adding permissions to wagon connection > > > > I've recently moved from maven 2.0.8 to 2.1.0 with a completely > > new local [.m2] repo. > > > > Any thoughts? Is the "not adding permissions" message a clue? Thanks. > > > > Brad > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
