July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22758) Context menu for multiple selected server modules has two 'remove' options

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22758?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22758: ---------------------------------- Attachment: remove.png > Context menu for multiple selected server modules has two 'remove' options > -------------------------------------------------------------------------- > > Key: JBIDE-22758 > URL: https://issues.jboss.org/browse/JBIDE-22758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > Attachments: remove.png, remove.png > > > I have multiple projects deployed to a server (wildfly in my case) and when I select at least 2 and right click on them, the context menu shows two remove entries. > They both have different icons and they pretty much do the same, except the second one also opens an empty shell along with the confirm prompt. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22758) Context menu for multiple selected server modules has two 'remove' options

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22758?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22758. --------------------------------- Verified in JBoss Tools 4.4.1.AM2. !remove.png! > Context menu for multiple selected server modules has two 'remove' options > -------------------------------------------------------------------------- > > Key: JBIDE-22758 > URL: https://issues.jboss.org/browse/JBIDE-22758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > Attachments: remove.png, remove.png > > > I have multiple projects deployed to a server (wildfly in my case) and when I select at least 2 and right click on them, the context menu shows two remove entries. > They both have different icons and they pretty much do the same, except the second one also opens an empty shell along with the confirm prompt. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[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 closed JBIDE-22772. --------------------------------- Since I just verified it, I'm also closing this. > 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 > Fix For: 4.4.1.AM2 > > > 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

1
0
0 / 0

[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 commented on JBIDE-22772: --------------------------------------- [~rob.stryker], which failures do you mean? The issue described in this JIRA was caused by the eap er zip not existing anymore. Furthermore, jenkins had a blocking issue where publishing of update sites didn't work, so all builds were broken. I can see blue builds now. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22805: ------------------------------------- The 2 requests (scale to 0 / scale pods) are not duplicates. Even though one PR might cover both cases. Added a warning when scaling to 0 is requested in JBIDE-22653 > Add Scale... menus on Pod resources > ----------------------------------- > > Key: JBIDE-22805 > URL: https://issues.jboss.org/browse/JBIDE-22805 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > > I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level. > I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23

by Wayne McDermott (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22288?page=com.atlassian.jira.plugi... ] Wayne McDermott commented on JBIDE-22288: ----------------------------------------- Maybe sudo ./devstudio SWT_GTK3=0 ? I will try tomorrow morning, I’m off to bed now. Good night. From: Ilya Buziuk (JIRA)<mailto:issues@jboss.org> Sent: Tuesday, July 26, 2016 9:15 PM To: wj.mcdermott(a)outlook.com<mailto:wj.mcdermott@outlook.com> Subject: [JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23 [https://static.jboss.org/developer/gravatar/3c0768b22fb3f6028fb7c22bcee22...] Ilya Buziuk<https://issues.jboss.org/secure/ViewProfile.jspa?name=ibuziuk> commented on [Bug] JBIDE-22288<https://issues.jboss.org/browse/JBIDE-22288> Re: VPE crashes studio with JRE fatal error on Fedora 23<https://issues.jboss.org/browse/JBIDE-22288> Wayne McDermott<https://issues.jboss.org/secure/ViewProfile.jspa?name=wjmcdermott>, oh, this looks weird indeed. Pavol Srna<https://issues.jboss.org/secure/ViewProfile.jspa?name=psrna>, Radim Hopp<https://issues.jboss.org/secure/ViewProfile.jspa?name=rhopp> could you guys repro this behavior^ ? [Add Comment] <https://issues.jboss.org/browse/JBIDE-22288#add-comment> Add Comment<https://issues.jboss.org/browse/JBIDE-22288#add-comment> This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) [Atlassian logo] > VPE crashes studio with JRE fatal error on Fedora 23 > ---------------------------------------------------- > > Key: JBIDE-22288 > URL: https://issues.jboss.org/browse/JBIDE-22288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.x > > Attachments: hs_err_pid2276.log.zip > > > Using VPE on Fedora ends up Studio crash > Works fine on Windows 10, Ubuntu 16.04 > More details can be found here - https://developer.jboss.org/message/955490 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22616) Red Hat Central crashes when SWT_WEBKIT2=1

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22616?page=com.atlassian.jira.plugi... ] Ilya Buziuk edited comment on JBIDE-22616 at 7/26/16 7:24 AM: -------------------------------------------------------------- PR created - NPE fix when browser name / version is not detected. Removing workaround for https://bugs.eclipse.org/bugs/show_bug.cgi?id=465822 was (Author: ibuziuk): PR created - NPE fix when browser name / version is not detected. Removing workaround for Bug 465822 > Red Hat Central crashes when SWT_WEBKIT2=1 > ------------------------------------------ > > Key: JBIDE-22616 > URL: https://issues.jboss.org/browse/JBIDE-22616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.x > > > This is a follow-up on JBDS-3953 > SWT_WEBKIT2=1 works around the problem of crashing Eclipse/devstudio on Fedora > But this prevent Central view from loading browser: > !https://issues.jboss.org/secure/attachment/12406478/12406478_Selection_003.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22288?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22288: ------------------------------------- [~wjmcdermott], oh, this looks weird indeed. [~psrna], [~rhopp] could you guys repro this behavior^ ? > VPE crashes studio with JRE fatal error on Fedora 23 > ---------------------------------------------------- > > Key: JBIDE-22288 > URL: https://issues.jboss.org/browse/JBIDE-22288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.x > > Attachments: hs_err_pid2276.log.zip > > > Using VPE on Fedora ends up Studio crash > Works fine on Windows 10, Ubuntu 16.04 > More details can be found here - https://developer.jboss.org/message/955490 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23

by Wayne McDermott (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22288?page=com.atlassian.jira.plugi... ] Wayne McDermott commented on JBIDE-22288: ----------------------------------------- I ran ./devstudio SWT_GTK3=0 .. but Eclipse is still running under GTK3 ! org.jboss.tools.vpe.xulrunner.XulRunnerException: Visual Page Editor for jsp/xhtml pages cannot be used under GTK3. Please run Eclipse with GTK2 very frustrating. > VPE crashes studio with JRE fatal error on Fedora 23 > ---------------------------------------------------- > > Key: JBIDE-22288 > URL: https://issues.jboss.org/browse/JBIDE-22288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.x > > Attachments: hs_err_pid2276.log.zip > > > Using VPE on Fedora ends up Studio crash > Works fine on Windows 10, Ubuntu 16.04 > More details can be found here - https://developer.jboss.org/message/955490 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Fred Bricon updated ERT-204: ---------------------------- Sprint: (was: devex #117 July 2016) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2016