[JBoss JIRA] (JBIDE-22772) jbosstools-server build fails - EAP 7 url needs updating
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22772?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22772:
-------------------------------------
Can you check if https://github.com/jbosstools/jbosstools-server/pull/436 works for you?
> jbosstools-server build fails - EAP 7 url needs updating
> --------------------------------------------------------
>
> Key: JBIDE-22772
> URL: https://issues.jboss.org/browse/JBIDE-22772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
>
> jbosstools-server build has been failing since July 11.
> This is the error:
> {code}
> 02:30:17 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error: Could not get content -> [Help 1]
> 02:30:17 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 02:30:17 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 02:30:17 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 02:30:17 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 02:30:17 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 02:30:17 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 02:30:17 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 02:30:17 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 02:30:17 at java.lang.reflect.Method.invoke(Method.java:498)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 02:30:17 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 02:30:17 at com.googlecode.WGet.execute(WGet.java:260)
> 02:30:17 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 02:30:17 ... 19 more
> 02:30:17 Caused by: org.apache.maven.plugin.MojoFailureException: Could not get content
> 02:30:17 at com.googlecode.WGet.execute(WGet.java:248)
> 02:30:17 ... 21 more
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] For more information about the errors and possible solutions, please read the following articles:
> 02:30:17 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] After correcting the problems, you can resume the build with the command
> 02:30:17 [ERROR] mvn <goals> -rf :itests
> {code}
> See here:
> https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom...
> It contains an outdated link to EAP 7 ER5 build. EAP 7 GA is available for some time now, so we need to update the url.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22772) jbosstools-server build fails - EAP 7 url needs updating
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22772?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-22772:
-------------------------------------
Assignee: Rob Stryker (was: Martin Malina)
> jbosstools-server build fails - EAP 7 url needs updating
> --------------------------------------------------------
>
> Key: JBIDE-22772
> URL: https://issues.jboss.org/browse/JBIDE-22772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> jbosstools-server build has been failing since July 11.
> This is the error:
> {code}
> 02:30:17 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error: Could not get content -> [Help 1]
> 02:30:17 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> 02:30:17 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> 02:30:17 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> 02:30:17 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> 02:30:17 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> 02:30:17 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> 02:30:17 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> 02:30:17 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 02:30:17 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 02:30:17 at java.lang.reflect.Method.invoke(Method.java:498)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> 02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> 02:30:17 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
> 02:30:17 at com.googlecode.WGet.execute(WGet.java:260)
> 02:30:17 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> 02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 02:30:17 ... 19 more
> 02:30:17 Caused by: org.apache.maven.plugin.MojoFailureException: Could not get content
> 02:30:17 at com.googlecode.WGet.execute(WGet.java:248)
> 02:30:17 ... 21 more
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] For more information about the errors and possible solutions, please read the following articles:
> 02:30:17 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 02:30:17 [ERROR]
> 02:30:17 [ERROR] After correcting the problems, you can resume the build with the command
> 02:30:17 [ERROR] mvn <goals> -rf :itests
> {code}
> See here:
> https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom...
> It contains an outdated link to EAP 7 ER5 build. EAP 7 GA is available for some time now, so we need to update the url.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22772) jbosstools-server build fails - EAP 7 url needs updating
by Martin Malina (JIRA)
Martin Malina created JBIDE-22772:
-------------------------------------
Summary: jbosstools-server build fails - EAP 7 url needs updating
Key: JBIDE-22772
URL: https://issues.jboss.org/browse/JBIDE-22772
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.1.AM2
Reporter: Martin Malina
Assignee: Martin Malina
jbosstools-server build has been failing since July 11.
This is the error:
{code}
02:30:17 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error: Could not get content -> [Help 1]
02:30:17 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (install-eap-7.0.0) on project itests: IO Error
02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
02:30:17 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
02:30:17 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
02:30:17 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
02:30:17 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
02:30:17 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
02:30:17 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
02:30:17 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
02:30:17 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
02:30:17 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
02:30:17 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
02:30:17 at java.lang.reflect.Method.invoke(Method.java:498)
02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
02:30:17 at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
02:30:17 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error
02:30:17 at com.googlecode.WGet.execute(WGet.java:260)
02:30:17 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
02:30:17 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
02:30:17 ... 19 more
02:30:17 Caused by: org.apache.maven.plugin.MojoFailureException: Could not get content
02:30:17 at com.googlecode.WGet.execute(WGet.java:248)
02:30:17 ... 21 more
02:30:17 [ERROR]
02:30:17 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
02:30:17 [ERROR]
02:30:17 [ERROR] For more information about the errors and possible solutions, please read the following articles:
02:30:17 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
02:30:17 [ERROR]
02:30:17 [ERROR] After correcting the problems, you can resume the build with the command
02:30:17 [ERROR] mvn <goals> -rf :itests
{code}
See here:
https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/pom...
It contains an outdated link to EAP 7 ER5 build. EAP 7 GA is available for some time now, so we need to update the url.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22622) Opening the Web Console in the embedded browser (by default) results in error
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22622?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22622.
---------------------------------
Verified in devstudio 10.0.1.AM2
Build id: AM2-v20160720-1632-B5674
> Opening the Web Console in the embedded browser (by default) results in error
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22622
> URL: https://issues.jboss.org/browse/JBIDE-22622
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: explorer, openshift, openshift_v3
> Fix For: 4.4.1.AM2
>
> Attachments: 2016-06-21 at 10-05-24.mp4
>
>
> The Web Console opens using whatever browser is set in Eclipse (internal by default). When using the default browser, after logging in, there's an error message stating "Server connection interrupted". This error occurs on OSX and Linux at least.
> I think the web console should be opened in the external browser in all cases.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-649) Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-649?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-649.
-----------------------------------
Verified with JBDS-IS 9.0.1.CR2 (contains org.jboss.tools.foundation.security.linux 1.2.1.Final-v20160408-2358-B112)
> Update org.jboss.tools.foundation.security.linux.feature to 1.2.1.Final
> -----------------------------------------------------------------------
>
> Key: JBTIS-649
> URL: https://issues.jboss.org/browse/JBTIS-649
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 4.0.0
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 9.0.1.GA
>
> Attachments: found1.png, jbdsis_security_bundle.png
>
>
> Currently, JBDS-IS 9.0.0.CR1 (and also the snapshot of CR1a) contains
> org.jboss.tools.foundation.security.linux 1.2.1.Beta2-v20160127-2129-B77
> but the JBDS 9.1.0.CR1a contains
> org.jboss.tools.foundation.security.linux 1.2.1.Final-v20160401-0436-B108
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default [ resolved making j7 default instead of j6]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21606.
---------------------------------
Nothing to do here. Closing.
> Consider using java 8 for EAP 6.4 by default [ resolved making j7 default instead of j6]
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-21606
> URL: https://issues.jboss.org/browse/JBIDE-21606
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM2
>
>
> Here's the problem that I just hit:
> I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime.
> Then on the project, I just Run -> Run on Server.
> The server started, but deployment failed on Unsupported version: 51.0
> Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6.
> So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19506:
-------------------------------------
Sprint: devex #118 July 2016 (was: devex #117 July 2016)
> Connection wizard, Connection: should have unit tests
> ------------------------------------------------------
>
> Key: JBIDE-19506
> URL: https://issues.jboss.org/browse/JBIDE-19506
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, tests
> Fix For: 4.4.x
>
> Original Estimate: 2 days
> Time Spent: 3 days
> Remaining Estimate: 3 days
>
> In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months