Hi, I experienced such an issue when rying to make maven work in a proxied environment... do you know whether there is a specific proxy configuration of that box or perhaps a firewall that you should take account for?
If so...you know well how to get rid of the problem... -- Daniele De Francesco Senior Java Architect Value Team Italia 2008/10/7 Patrizio Munzi <[EMAIL PROTECTED]> > Hi, > > I checked the file /etc/resolv.conf > and it seems ok. > Also the command: > > ------------------------------------------------------------------------------------------ > [EMAIL PROTECTED] ~]$ telnet repo1.maven.org 80 > Trying 38.97.124.18... > Connected to repo1.maven.org. > Escape character is '^]'. > ^C > Connection to repo1.maven.org closed by foreign host. > works properly. > > ------------------------------------------------------------------------------------------ > Here's my exception stack trace. Anyway I'm quite sure that it's a > network configuration problem. > > ------------------------------------------------------------------------------------------ > [EMAIL PROTECTED] ~]$ mvn -X archetype:create -DgroupId=test -DartifactId=test > + Error stacktraces are turned on. > Maven version: 2.0.9 > Java version: 1.6.0_06 > OS name: "sunos" version: "5.10" arch: "sparc" Family: "unix" > [DEBUG] Building Maven user-level plugin registry from: > '/export/home/munzi/.m2/plugin-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: > '/usr/local/maven-2.0.9/conf/plugin-registry.xml' > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'archetype'. > [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not > be retrieved from repository: central due to an error: Error > transferring file > [DEBUG] Exception > 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(DefaultWagonManager.java:470) > at > > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:370) > at > > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:97) > at > > org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(DefaultPluginMappingManager.java:103) > at > > org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(DefaultPluginMappingManager.java:87) > at > > org.apache.maven.plugin.DefaultPluginMappingManager.getByPrefix(DefaultPluginMappingManager.java:61) > at > > org.apache.maven.plugin.DefaultPluginManager.getPluginDefinitionForPrefix(DefaultPluginManager.java:154) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1468) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:405) > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) > 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.java:39) > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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: java.net.UnknownHostException: repo1.maven.org > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) > 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:394) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) > at sun.net.www.http.HttpClient.<init>(HttpClient.java:233) > at sun.net.www.http.HttpClient.New(HttpClient.java:306) > at sun.net.www.http.HttpClient.New(HttpClient.java:323) > at > > sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:788) > at > > sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:729) > at > > sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:654) > at > > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:977) > at > > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:83) > ... 22 more > ------------------------------------------------------------------- > > BR > Patrizio > > Olivier Lamy wrote: > > Hi, > > I use maven with solaris 10 all the day. > > > > Check the file : resolv.conf with the cli cat /etc/resolv.conf > > > > You should see something like > > > > ; try dns name server > > nameserver dns server ip > > nameserver secondary dns server ip > > > > And try the cli : > > > > bash-3.00$ telnet repo1.maven.org 80 > > Trying 38.97.124.18... > > Connected to repo1.maven.org. > > Escape character is '^]'. > > ^C^] > > > > > > -- > > Olivier > > > > 2008/10/6 Wayne Fay <[EMAIL PROTECTED]>: > > > >> Seems like your DNS resolution is not working properly. You need to > >> talk to who ever your sysadmin is to get that fixed, and then Maven > >> should work fine. > >> > >> And if *you* are the sysadmin of this box, you need to get help from a > >> "Solaris beginners" forum to get your box set up and working on the > >> Internet properly, then try Maven again. > >> > >> Wayne > >> > >> On Mon, Oct 6, 2008 at 9:15 AM, 陈思淼 <[EMAIL PROTECTED]> wrote: > >> > >>> you can ping repo1.maven.org to verify the network working. > >>> Maven can work in Solaris of cause because that SUN's home platform. > >>> and maven is a java program. > >>> > >>> 2008/10/7 Patrizio Munzi <[EMAIL PROTECTED]> > >>> > >>> > >>>> Hi everybody, > >>>> > >>>> I've been trying to make maven work on SUN Solaris 10 for the last few > >>>> days, but since I'm not a Solaris administration expert I had no luck. > >>>> I have the following exception: > >>>> > >>>> Caused by: java.net.UnknownHostException: repo1.maven.org > >>>> > >>>> I think it's related to some Solaris network configurations, but I > don't > >>>> know how to solve them. > >>>> > >>>> Can anyone help me...? > >>>> > >>>> Thanks > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>> For additional commands, e-mail: [EMAIL PROTECTED] > >>>> > >>>> > >>>> > > -- > > *Patrizio Munzi* > Product Specialist > Viale Bruno Buozzi, 19 - 00197 Roma (Italy) > tel: +39 06 4543 3540 > fax: +39 06 4543 3587 > mobile: +39 393 7195 164 > mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > web: http://www.eris4.com <http://www.eris4.com/> > skype: eris4_munzi <skype:eris4_munzi?add> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
