appfuse:full-source throwing SocketException
|
|
Fringe
|
Hi,
When I try to run mvn appfuse:full-source I am getting a Connection refused SocketException. I have run this command multiple times in the past couple of days and it has worked fine but all of a sudden it started throwing this exception a couple of hours back. Since it already had worked before and the necessary plugin files must have been already downloaded I wonder why it is trying to access the internet. I tried disabling my internet connection and I got a UnknownHostException for appfuse.dev.java.net. I tried accessing the url, it was down. Is this the reason why full-source is failing? Even if this is the reason I do not understand why it is accessing the internet when all the plugin related files must already be there in the local repository. Full stacktrace: java.net.ConnectException: Connection refused: connect at org.apache.tools.ant.taskdefs.Get.execute(Get.java:80) at org.appfuse.mojo.installer.InstallSourceMojo.addModuleDependencies(InstallSourceMojo.java:653) at org.appfuse.mojo.installer.InstallSourceMojo.addModuleDependencies(InstallSourceMojo.java:626) at org.appfuse.mojo.installer.InstallSourceMojo.execute(InstallSourceMojo.java:215) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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.ConnectException: Connection refused: 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.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:550) at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:141) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:271) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:328) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:731) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158) at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:133) at org.apache.tools.ant.taskdefs.Get.doGet(Get.java:158) at org.apache.tools.ant.taskdefs.Get.execute(Get.java:76) ... 21 more --- Nested Exception --- java.net.ConnectException: Connection refused: 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.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:550) at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:141) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:271) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:328) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:731) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158) at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:133) at org.apache.tools.ant.taskdefs.Get.doGet(Get.java:158) at org.apache.tools.ant.taskdefs.Get.execute(Get.java:76) at org.appfuse.mojo.installer.InstallSourceMojo.addModuleDependencies(InstallSourceMojo.java:653) at org.appfuse.mojo.installer.InstallSourceMojo.addModuleDependencies(InstallSourceMojo.java:626) at org.appfuse.mojo.installer.InstallSourceMojo.execute(InstallSourceMojo.java:215) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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) Thanks, Chris. |
||||||||||||||||
mraible
|
The reason is because full-source connects to SVN and "exports" the source files into your project. I got a similar error from AppFuse's build server, so I believe java.net's SVN had a hiccup. Appears to be back now.
Matt On Tue, Nov 3, 2009 at 12:50 PM, Fringe <[hidden email]> wrote:
|
||||||||||||||||
|
Fringe
|
Thank you, Matt. Should it not work straight if the SVN/internet is down by taking the source files which were downloaded the last time full-source was run? Just meant to ask if this is an exception in the way Maven plugins work.
Chirs.
|
||||
|
mraible
|
Internally, we use the "svn export" command and put them directly into your project. The "full-source" command should only need to be run once. Is there a reason you're running it multiple times?
I've thought about changing things so the source can be pulled from the source JARs in Maven's repository, but that'd take quite a bit of work. Matt On Wed, Nov 4, 2009 at 10:41 AM, Fringe <[hidden email]> wrote:
|
||||||||||||||||
|
Fringe
|
Matt,
Yeah, it is ideally run just once. May I say it is run as many times the archetype is created? I was fiddling around with Appfuse and eclipse. Basically trying to figure out differences between m2ecllipse and mvn eclipse:eclipse so created the archetypes more than once. Another instance when I faced the problem was during an introductory Appfuse session I was conducting. I had everything set just the hour before but while the developers started their hands-on, the java.net server seemed to be down. I think it is fine this way. Thanks, Chris.
|
||||||||||||||||
|
mraible
|
One thing you could do is to grab AppFuse from SVN and stick it in your own SVN repository. The URL and tag are overridable:
/** * The directory containing the source code. * * @parameter expression="${appfuse.trunk}" default-value="https://appfuse.dev.java.net/svn/appfuse/" */ private String trunk; /** * The tag containing the source code - defaults to '/trunk', but you may want to set it to '/tags/TAGNAME' * * @parameter expression="${appfuse.tag}" default-value="trunk/" */ private String tag; This means you can do -Dappfuse.trunk= or specify <trunk>...</trunk> in the configuration settings. The username and password (guest/(blank)) are hard-coded, but we could certainly change that. Matt On Fri, Nov 6, 2009 at 5:02 AM, Fringe <[hidden email]> wrote:
|
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
