It fails during "mvn install" of the child artifact. If a child pom depends on something that has repo info configured inside it improperly, then when you try to run mvn install of the child pom, things go nuts and the url is NOT reported (mvn 2.0.9).
We recently transitioned away from a windows based archiva server to a solaris based one - also transitioning to a new cname. This particular parent pom was overlooked when we made our switch. -----Original Message----- From: Tim [mailto:[email protected]] Sent: Mon 12/22/2008 6:28 PM To: Maven Users List Subject: Re: mvn deploy - no route to host exception I'm sry I'm a bit confused what plugin/goal you are executing.I get a big fat Error deploying artifact: Failed to transfer file: http://gemini:8081/nexus/content/repositories/snapshots/test/test-SNAPSHOT/test-20081222.232254-1.jar. Return code is: 405 When I misconfigure my deploy repository url running $ mvn deploy And that is from a submodule as well. On Mon, Dec 22, 2008 at 3:55 PM, EJ Ciramella <[email protected]>wrote: > The output with -X -e is attached. > > Please note, the problem was the parent of the module I was trying to > deploy had a misconfigured repository inside it, not the actual module I > was attempting to deploy. > > > No route to host: connect > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error retrieving > previous build number for artifact > 'com.upromise.atgModule:olmAtgCommon:atg-module': repository metadata > for: 's > napshot com.upromise.atgModule:olmAtgCommon:2009-P2008006-SNAPSHOT' > could not be retrieved from repository: bertha due to an error: Error > transferring file > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default > LifecycleExecutor.java:583) > 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error > retrieving previous build number for artifact > 'com.upromise.atgModule:olmAtgCommon:atg-module': repository metadata > for: > 'snapshot com.upromise.atgModule:olmAtgCommon:2009-P2008006-SNAPSHOT' > could not be retrieved from repository: bertha due to an error: Error > transferring file > at > org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa > nager.java:451) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default > LifecycleExecutor.java:558) > ... 16 more > Caused by: > org.apache.maven.artifact.deployer.ArtifactDeploymentException: 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 > at > org.apache.maven.artifact.transform.SnapshotTransformation.transformForD > eployment(SnapshotTransformation.java:106) > 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:162) > ... 18 more > Caused by: > org.apache.maven.artifact.repository.metadata.RepositoryMetadataResoluti > onException: repository metadata for: 'snapshot > com.upromise.atgModule:olmAtgCommon:2009-P2008006-SNAP > SHOT' could not be retrieved from repository: bertha due to an error: > Error transferring file > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataM > anager.resolveAlways(DefaultRepositoryMetadataManager.java:352) > at > org.apache.maven.artifact.transform.SnapshotTransformation.resolveLatest > SnapshotBuildNumber(SnapshotTransformation.java:161) > at > org.apache.maven.artifact.transform.SnapshotTransformation.transformForD > eployment(SnapshotTransformation.java:100) > ... 21 more > Caused by: org.apache.maven.wagon.TransferFailedException: Error > transferring file > at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData > (LightweightHttpWagon.java:104) > at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(Defa > ultWagonManager.java:470) > 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) > ... 23 more > Caused by: java.net.NoRouteToHostException: No route to host: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.Socket.connect(Socket.java:519) > at java.net.Socket.connect(Socket.java:469) > at sun.net.NetworkClient.doConnect(NetworkClient.java:157) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:382) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:509) > at sun.net.www.http.HttpClient.<init>(HttpClient.java:231) > at sun.net.www.http.HttpClient.New(HttpClient.java:304) > at sun.net.www.http.HttpClient.New(HttpClient.java:316) > at > sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConn > ection.java:817) > at > sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnecti > on.java:769) > at > sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.ja > va:694) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnec > tion.java:938) > at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData > (LightweightHttpWagon.java:83) > ... 28 more > > -----Original Message----- > From: Brian E. Fox [mailto:[email protected]] > Sent: Monday, December 22, 2008 3:41 PM > To: Maven Users List > Subject: RE: mvn deploy - no route to host exception > > -e will also show the full stack trace. > > -----Original Message----- > From: Tim [mailto:[email protected]] > Sent: Monday, December 22, 2008 2:48 PM > To: Maven Users List > Subject: Re: mvn deploy - no route to host exception > > I had this problem recently but I thought that -X showed me what it was > trying to connect to. That didn't work for you? > On Mon, Dec 22, 2008 at 1:45 PM, EJ Ciramella > <[email protected]>wrote: > > > I said "please" didn't I ;-) > > > > Point taken - just posting here as well so people who google "No path > to > > host exceptions" with regard to maven 2 may diagnose their own > problems > > quickly. > > > > Thank you! > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf Of > Baptiste > > MATHUS > > Sent: Monday, December 22, 2008 2:33 PM > > To: Maven Users List > > Subject: Re: mvn deploy - no route to host exception > > > > Hi, > > First, I thought that saying hello and thanks was quite simple. > > Second, remember this is a user mailing list, with the flow of mails > > coming through it, your question is lekily to be forgotten. So, if you > > > have an improvement request, you'd better file it if you ever want to > > see something coming (and obviously, "chasing" the patch yourself will > > > help :-)). > > > > Cheers. > > > > 2008/12/22 EJ Ciramella <[email protected]> > > > > > Can someone please update the deploy plugin such that when people > get > > > exceptions like the "no route to host" exception, it prints out the > > > host it tried connecting to? > > > > > > That had me chasing my tail and tracking back through all my > > > dependencies this weekend.... > > > > > > > > > > > -- > > Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez > un > > castor ! > > > > --------------------------------------------------------------------- > > 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] > > > --------------------------------------------------------------------- > 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]
