[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21294.
---------------------------------
Resolution: Done
I've fixed the NPE at least. This still doesn't solve why you can't find the vagrant command, but my improvements in error messaging instruct user to look at their path and modify it.
> NPE when starting CDK server
> ----------------------------
>
> Key: JBIDE-21294
> URL: https://issues.jboss.org/browse/JBIDE-21294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE:
> {code}
> An internal error occurred during: "Starting cdk-v2 CDK Server".
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:277)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> I did add the user credentials in the server editor.
> Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow.
> [1] https://github.com/redhat-developer-tooling/openshift-vagrant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21172) CDK server in Starting state and cannot be stopped with wrong path to vagrant
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21172?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21172:
--------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> CDK server in Starting state and cannot be stopped with wrong path to vagrant
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21172
> URL: https://issues.jboss.org/browse/JBIDE-21172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> When I first set up a CDK 2 Beta3 server adapter in Eclipse, it had the launch config set up with the wrong path to vagrant - /usr/bin/vagrant instead of /usr/local/bin/vagrant which is the default location on OS X - I didn't notice this and just tried to start the adapter.
> Obviously it failed, but I was left in a state where the server was Starting and I couldn't stop it unless I restarted the IDE.
> I think it should fail more gracefully.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21232) parent pom should never allow skipTests to prevent download of required libraries
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21232?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21232:
------------------------------------
Perhaps... but with less discussion. :D
> parent pom should never allow skipTests to prevent download of required libraries
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21232
> URL: https://issues.jboss.org/browse/JBIDE-21232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, forge, hibernate, openshift
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> {quote}
> {quote}I think at this time obviously we have to change
> maven-dependency-plugin declaration
> in *parent/pom.xml#build/pluginManagement* to never skip downloading
> dependencies, because it is most common use case. After it is done we can
> remove unnecessary *<skip>false</skip>* throughout the projects.{quote}
> Yes - your conclusion matches mine on the jira and what mistria suggestion for fixes
> and with my updates handles.
> Can you make it happen ? :)
> {quote}
> If there are libs for (2) and (3) downloaded from external URL using
> download-maven-plugin/maven-download-plugin we should probably move them to
> locus.{quote}
> Main problem I know is forge, hibernate and openshift afaik.
> forge and openshift would not be able to move very fast if we moved their libs for Locus.
> Hibernate - we don't actually want/intend to expose the internal apis of hibernate so not
> sure if pushing all variations of hibernate into Locus is such a good idea....but it could
> be considered.
> One thing that might be worth looking for are those bundling mockito or other testing libs
> that we might already have put into locus or use from orbit so these are not even relevant anymore.{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21296) failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21296?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21296:
------------------------------------
This is the step that failed:
{code}
<execution>
<id>install-eap-seam-gen</id>
<phase>pre-integration-test</phase>
<goals>
<goal>wget</goal>
</goals>
<configuration>
<url>http://download.jboss.org/jbosstools/test-runtimes/rhds-seam-gen-patch.zip</url>
<md5>79b37541804f49844ea7322c0ff599c1</md5>
<unpack>true</unpack>
<outputDirectory>${requirementsDirectory}/jboss-eap-4.3/seam</outputDirectory>
<skip>${skipPrivateRequirements}</skip>
</configuration>
</execution>{code} -- https://github.com/jbosstools/jbosstools-javaee/blob/jbosstools-4.3.1.Bet...
> failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
> --------------------------------------------------------------------------
>
> Key: JBIDE-21296
> URL: https://issues.jboss.org/browse/JBIDE-21296
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, seam2
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
>
> {code}
> 18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
> com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
> on project org.jboss.tools.seam.core.test: IO Error
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 18:17:13 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 18:17:13 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 18:17:13 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 18:17:13 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 18:17:13 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 18:17:13 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:17:13 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:17:13 at java.lang.reflect.Method.invoke(Method.java:497)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 18:17:13 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:260)
> 18:17:13 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:17:13 ... 19 more
> 18:17:13 Caused by: java.io.EOFException
> 18:17:13 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
> 18:17:13 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
> 18:17:13 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
> 18:17:13 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
> 18:17:13 at com.googlecode.DownloadCache.loadIndex(DownloadCache.java:103)
> 18:17:13 at com.googlecode.DownloadCache.install(DownloadCache.java:80)
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:252)
> 18:17:13 ... 21 more
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21296) failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21296?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21296 at 12/10/15 6:25 PM:
--------------------------------------------------------------
This is the step that failed:
{code}
<execution>
<id>install-eap-seam-gen</id>
<phase>pre-integration-test</phase>
<goals>
<goal>wget</goal>
</goals>
<configuration>
<url>http://download.jboss.org/jbosstools/test-runtimes/rhds-seam-gen-patch.zip</url>
<md5>79b37541804f49844ea7322c0ff599c1</md5>
<unpack>true</unpack>
<outputDirectory>${requirementsDirectory}/jboss-eap-4.3/seam</outputDirectory>
<skip>${skipPrivateRequirements}</skip>
</configuration>
</execution>{code} -- https://github.com/jbosstools/jbosstools-javaee/blob/jbosstools-4.3.1.Bet...
was (Author: nickboldt):
This is the step that failed:
{code}
<execution>
<id>install-eap-seam-gen</id>
<phase>pre-integration-test</phase>
<goals>
<goal>wget</goal>
</goals>
<configuration>
<url>http://download.jboss.org/jbosstools/test-runtimes/rhds-seam-gen-patch.zip</url>
<md5>79b37541804f49844ea7322c0ff599c1</md5>
<unpack>true</unpack>
<outputDirectory>${requirementsDirectory}/jboss-eap-4.3/seam</outputDirectory>
<skip>${skipPrivateRequirements}</skip>
</configuration>
</execution>{code} -- https://github.com/jbosstools/jbosstools-javaee/blob/jbosstools-4.3.1.Bet...
> failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
> --------------------------------------------------------------------------
>
> Key: JBIDE-21296
> URL: https://issues.jboss.org/browse/JBIDE-21296
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, seam2
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
>
> {code}
> 18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
> com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
> on project org.jboss.tools.seam.core.test: IO Error
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 18:17:13 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 18:17:13 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 18:17:13 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 18:17:13 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 18:17:13 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 18:17:13 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:17:13 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:17:13 at java.lang.reflect.Method.invoke(Method.java:497)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 18:17:13 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:260)
> 18:17:13 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:17:13 ... 19 more
> 18:17:13 Caused by: java.io.EOFException
> 18:17:13 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
> 18:17:13 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
> 18:17:13 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
> 18:17:13 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
> 18:17:13 at com.googlecode.DownloadCache.loadIndex(DownloadCache.java:103)
> 18:17:13 at com.googlecode.DownloadCache.install(DownloadCache.java:80)
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:252)
> 18:17:13 ... 21 more
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21296) failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21296?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21296:
--------------------------------------
Assignee: Alexey Kazakov
> failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
> --------------------------------------------------------------------------
>
> Key: JBIDE-21296
> URL: https://issues.jboss.org/browse/JBIDE-21296
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, seam2
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
>
> {code}
> 18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
> com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
> on project org.jboss.tools.seam.core.test: IO Error
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 18:17:13 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 18:17:13 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 18:17:13 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 18:17:13 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 18:17:13 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 18:17:13 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:17:13 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:17:13 at java.lang.reflect.Method.invoke(Method.java:497)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 18:17:13 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:260)
> 18:17:13 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:17:13 ... 19 more
> 18:17:13 Caused by: java.io.EOFException
> 18:17:13 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
> 18:17:13 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
> 18:17:13 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
> 18:17:13 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
> 18:17:13 at com.googlecode.DownloadCache.loadIndex(DownloadCache.java:103)
> 18:17:13 at com.googlecode.DownloadCache.install(DownloadCache.java:80)
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:252)
> 18:17:13 ... 21 more
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21296) failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21296?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21296:
-------------------------------
Description:
{code}
18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
on project org.jboss.tools.seam.core.test: IO Error
18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
18:17:13 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
18:17:13 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
18:17:13 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
18:17:13 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
18:17:13 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
18:17:13 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
18:17:13 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
18:17:13 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
18:17:13 at java.lang.reflect.Method.invoke(Method.java:497)
18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
18:17:13 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
18:17:13 at com.googlecode.WGet.execute(WGet.java:260)
18:17:13 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
18:17:13 ... 19 more
18:17:13 Caused by: java.io.EOFException
18:17:13 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
18:17:13 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
18:17:13 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
18:17:13 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
18:17:13 at com.googlecode.DownloadCache.loadIndex(DownloadCache.java:103)
18:17:13 at com.googlecode.DownloadCache.install(DownloadCache.java:80)
18:17:13 at com.googlecode.WGet.execute(WGet.java:252)
18:17:13 ... 21 more
{code}
-- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
was:
{code}
18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
on project org.jboss.tools.seam.core.test: IO Error{code}
-- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> failure in org.jboss.tools.seam.core.test - could not install-eap-seam-gen
> --------------------------------------------------------------------------
>
> Key: JBIDE-21296
> URL: https://issues.jboss.org/browse/JBIDE-21296
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, seam2
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
>
> {code}
> 18:17:13 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
> com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-seam-gen)
> on project org.jboss.tools.seam.core.test: IO Error
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 18:17:13 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 18:17:13 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 18:17:13 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 18:17:13 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 18:17:13 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 18:17:13 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 18:17:13 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 18:17:13 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 18:17:13 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 18:17:13 at java.lang.reflect.Method.invoke(Method.java:497)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 18:17:13 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 18:17:13 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:260)
> 18:17:13 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 18:17:13 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 18:17:13 ... 19 more
> 18:17:13 Caused by: java.io.EOFException
> 18:17:13 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)
> 18:17:13 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)
> 18:17:13 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)
> 18:17:13 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
> 18:17:13 at com.googlecode.DownloadCache.loadIndex(DownloadCache.java:103)
> 18:17:13 at com.googlecode.DownloadCache.install(DownloadCache.java:80)
> 18:17:13 at com.googlecode.WGet.execute(WGet.java:252)
> 18:17:13 ... 21 more
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months