May 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4770) Update devstudio installer tests after rebranding

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4770?page=com.atlassian.jira.plugin.... ] Ondrej Dockal closed JBDS-4770. ------------------------------- > Update devstudio installer tests after rebranding > ------------------------------------------------- > > Key: JBDS-4770 > URL: https://issues.jboss.org/browse/JBDS-4770 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: install-tests > Affects Versions: 12.12.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.12.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26622) Update 4.12.0.AM1 Target Platform (Docker tooling, ...) for 2019-06.M1

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26622?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26622. --------------------------------- We had no issue with this TP update. > Update 4.12.0.AM1 Target Platform (Docker tooling, ...) for 2019-06.M1 > ---------------------------------------------------------------------- > > Key: JBIDE-26622 > URL: https://issues.jboss.org/browse/JBIDE-26622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.12.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.12.0.AM1 > > Attachments: p2diff_log_jbosstools_2019-04-04_16-45.txt, p2diff_log_jbosstools_2019-04-09_02-17.txt, p2diff_log_jbosstools_2019-04-21_10-50.txt > > > Jira for tracking TP updates: > [~jeffmaury] Can you please update docker tooling on TP? The latest version includes fixes for running ITests with JDK1.8: https://git.eclipse.org/r/#/c/139834/ > Thank you! -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26598) Unable to connect to "local" JMX process when instance launched with JDK 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26598. --------------------------------- I consider this issue to be closed as of devstudio 12.12.0.-v20190520-0258-B4567. Except, there is still a feature of JVM not allowing to connect the the jvm instance itself. > Unable to connect to "local" JMX process when instance launched with JDK 11 > --------------------------------------------------------------------------- > > Key: JBIDE-26598 > URL: https://issues.jboss.org/browse/JBIDE-26598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.11.0.Final > Reporter: Aurélien Pupier > Assignee: Ondrej Dockal > Priority: Blocker > Fix For: 4.11.0.Final > > > {code} > org.jboss.tools.jmx.local > Error > Wed Mar 27 09:25:29 CET 2019 > Unable to connect to jvm > org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException: Could not get JMX service URL (PID: 9470) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:462) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:445) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:233) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:213) > at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect(JvmConnectionWrapper.java:118) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26635) Job devstudio.product_master is red

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26635?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26635. --------------------------------- Builds went to green after fix. > Job devstudio.product_master is red > ----------------------------------- > > Key: JBIDE-26635 > URL: https://issues.jboss.org/browse/JBIDE-26635 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.12.0.AM1 > Environment: CentralCI > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.12.0.AM1 > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Job Fails with IO Error: > {code:java} > [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project com.jboss.devstudio.core.central: IO Error: Could not get content -> [Help 1] > 06:48:57 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project com.jboss.devstudio.core.central: IO Error > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) > 06:48:57 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) > 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) > 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) > 06:48:57 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) > 06:48:57 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) > 06:48:57 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > 06:48:57 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > 06:48:57 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > 06:48:57 at java.lang.reflect.Method.invoke (Method.java:498) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) > 06:48:57 Caused by: org.apache.maven.plugin.MojoExecutionException: IO Error > 06:48:57 at com.googlecode.WGet.execute (WGet.java:260) > 06:48:57 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134) > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) > 06:48:57 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) > 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) > 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) > 06:48:57 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) > 06:48:57 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) > 06:48:57 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > 06:48:57 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > 06:48:57 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > 06:48:57 at java.lang.reflect.Method.invoke (Method.java:498) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) > 06:48:57 Caused by: org.apache.maven.plugin.MojoFailureException: Could not get content > 06:48:57 at com.googlecode.WGet.execute (WGet.java:248) > 06:48:57 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:134) > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) > 06:48:57 at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) > 06:48:57 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:51) > 06:48:57 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) > 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309) > 06:48:57 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194) > 06:48:57 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107) > 06:48:57 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955) > 06:48:57 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290) > 06:48:57 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194) > 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > 06:48:57 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) > 06:48:57 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) > 06:48:57 at java.lang.reflect.Method.invoke (Method.java:498) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) > 06:48:57 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Ondrej Dockal closed JBDS-4730. ------------------------------- Rebranding is done. In case that we need to update "logos" as mentioned above, please open new jira. > [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.11.0.AM1 > > Attachments: CR-Studio_wordmarks.zip, RHCRS_graphics.zip > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26565) Update 4.11.0.Final TP

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26565?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26565. --------------------------------- > Update 4.11.0.Final TP > ---------------------- > > Key: JBIDE-26565 > URL: https://issues.jboss.org/browse/JBIDE-26565 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.11.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.Final > > Attachments: p2diff.txt, p2diff_log_jbosstools_2019-03-08_06-47.txt, p2diff_log_jbosstools_2019-03-14_08-36.txt, p2diff_log_jbosstools_2019-03-15_02-32.txt, p2diff_log_jbosstools_2019-03-21_16-02.txt > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26388) TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26388?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26388. --------------------------------- > TP: create target platform based on Eclipse 4.10 (Simrel 2018-12) > ----------------------------------------------------------------- > > Key: JBIDE-26388 > URL: https://issues.jboss.org/browse/JBIDE-26388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Major > Labels: releasework > Fix For: 4.11.0.Final > > Attachments: 4.10.0.AM1.M1-4.10.0.AM1.M2.p2diff.txt, jbosstools-multiple-considerversions-4.9.0.Final-4.10.0.AM1.p2diff, jbosstools-multiple-ignoreversions-4.9.0.Final-4.10.0.AM1.p2diff > > > In order to start Eclipse 4.10-based builds, we need an updated target platform. > Note that Eclipse 4.10 drops support for win32 and lin32 platforms, so poms will need to be updated accordingly. 32-bit is dead, long live 64-bit! > For sprint 156 / AM1: simrel M1 > For sprint 157 / AM1: simrel M2 > For sprint 158 / GA: simrel M3/RC1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-731) [GTK] Shell.print(GC) not implemented [EBZ#547557]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-731?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-731: --------------------------------- Sprint: devex #167 June 2019 Assignee: Eric Williams > [GTK] Shell.print(GC) not implemented [EBZ#547557] > -------------------------------------------------- > > Key: ERT-731 > URL: https://issues.jboss.org/browse/ERT-731 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.13, SWT, bzira > > Created attachment 278707 > Snippet > Shell.print(GC) is overridden to do nothing and returns false. > https://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/bundle... > Just removing the override seems to work, however take note that it only prints the client area, it doesn't print the Shell trimmings. It should be printed to a GC drawing to an Image with bounds equal to Shell.getClientArea(), not Shell.getBounds(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-732) [GTK] Implement native ImageLoader [EBZ#545032]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-732?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-732: --------------------------------- Sprint: devex #167 June 2019 Assignee: Eric Williams > [GTK] Implement native ImageLoader [EBZ#545032] > ----------------------------------------------- > > Key: ERT-732 > URL: https://issues.jboss.org/browse/ERT-732 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.13, SWT, bzira > > Implement a native version of ImageLoader, using GdkPixbuf API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-730) [GTK3] Regression: ImageLoader.save() no longer works [EBZ#547529]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-730?page=com.atlassian.jira.plugin.sy... ] Eric Williams resolved ERT-730. ------------------------------- Resolution: Done > [GTK3] Regression: ImageLoader.save() no longer works [EBZ#547529] > ------------------------------------------------------------------ > > Key: ERT-730 > URL: https://issues.jboss.org/browse/ERT-730 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: 4.12_RC1, SWT, bzira > > Created attachment 278682 > Snippet > We have a feature in our application that takes a snapshot of a Control and saves it to a file using ImageLoader. This no longer works properly in 4.12 and creates a corrupted image. > The included snippet can be used to run the same code that works in 4.11. > Bisecting shows that the problem was introduced with Bug 545032. > Reproduced with GTK 3.22.30 on Ubuntu 18.04. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2019