June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24567) org.jboss.tools.foundation.security.linux displays localization keys instead of correct labels

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24567?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24567: ------------------------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=518811 https://github.com/jbosstools/jbosstools-base/pull/585 I think this works. See comments on bugzilla. > org.jboss.tools.foundation.security.linux displays localization keys instead of correct labels > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-24567 > URL: https://issues.jboss.org/browse/JBIDE-24567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Environment: Devstudio 11.0.0.AM1-v20170615-0541-B336 > Reporter: Radim Hopp > Assignee: Rob Stryker > Attachments: image-2017-06-21-11-44-19-905.png, image-2017-06-21-11-44-49-953.png > > > No localization key defined in fragment.properties is displayed correctly. > !image-2017-06-21-11-44-19-905.png|thumbnail! > !image-2017-06-21-11-44-49-953.png|thumbnail! > This was definitely ok in 10.4. It seems that nothing changed on our side. Maybe some upstream change in oxygen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24567) org.jboss.tools.foundation.security.linux displays localization keys instead of correct labels

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24567?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-24567: ----------------------------------- Assignee: Rob Stryker > org.jboss.tools.foundation.security.linux displays localization keys instead of correct labels > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-24567 > URL: https://issues.jboss.org/browse/JBIDE-24567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Environment: Devstudio 11.0.0.AM1-v20170615-0541-B336 > Reporter: Radim Hopp > Assignee: Rob Stryker > Attachments: image-2017-06-21-11-44-19-905.png, image-2017-06-21-11-44-49-953.png > > > No localization key defined in fragment.properties is displayed correctly. > !image-2017-06-21-11-44-19-905.png|thumbnail! > !image-2017-06-21-11-44-49-953.png|thumbnail! > This was definitely ok in 10.4. It seems that nothing changed on our side. Maybe some upstream change in oxygen? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24548) Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24548?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-24548: ------------------------------------------ Created an issue in s2i-wildfly project: https://github.com/openshift-s2i/s2i-wildfly/issues/131. You can find all the details there. > Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly > -------------------------------------------------------------------------------- > > Key: JBIDE-24548 > URL: https://issues.jboss.org/browse/JBIDE-24548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Environment: Running on Mac 10.12.4 > JBDS > Version: 10.3.0.GA > Build id: GA-v20170218-1636-B94 > Build date: 20170218-1636 > Installed minishift v1.0.1 > Reporter: Veer Muchandi > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > > * Created a Wildfly application on openshift web-ui > * Setup a server adapter > * Imported application to JBDS > * Made code changes and saved. > Result: > While the data seems to be exchanged, the changes are not synced with the pod and the application is not updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4449) DevSuite Installer won't install VirtualBox on Mac

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4449?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4449: ------------------------------ Issue Type: Bug (was: Enhancement) > DevSuite Installer won't install VirtualBox on Mac > -------------------------------------------------- > > Key: JBDS-4449 > URL: https://issues.jboss.org/browse/JBDS-4449 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac OSX, 10.12.5 > Reporter: Bob Davis > Fix For: 11.0.0.AM2 > > > Installer detected an older version of Virtual box than was required, so I uninstalled that (by deleting the application) and went back to the installer, which did a new scan and offered the latest available version, but left the checkbox unselectable - there was no way to get it to install any version of VirtualBox, and no error message given. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4449) DevSuite Installer won't install VirtualBox on Mac

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4449?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4449: ------------------------------ Fix Version/s: 11.0.0.AM2 > DevSuite Installer won't install VirtualBox on Mac > -------------------------------------------------- > > Key: JBDS-4449 > URL: https://issues.jboss.org/browse/JBDS-4449 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac OSX, 10.12.5 > Reporter: Bob Davis > Fix For: 11.0.0.AM2 > > > Installer detected an older version of Virtual box than was required, so I uninstalled that (by deleting the application) and went back to the installer, which did a new scan and offered the latest available version, but left the checkbox unselectable - there was no way to get it to install any version of VirtualBox, and no error message given. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4449) DevSuite Installer won't install VirtualBox on Mac

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4449?page=com.atlassian.jira.plugin.... ] Jan Richter reassigned JBDS-4449: --------------------------------- Assignee: Jan Richter > DevSuite Installer won't install VirtualBox on Mac > -------------------------------------------------- > > Key: JBDS-4449 > URL: https://issues.jboss.org/browse/JBDS-4449 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac OSX, 10.12.5 > Reporter: Bob Davis > Assignee: Jan Richter > Fix For: 11.0.0.AM2 > > > Installer detected an older version of Virtual box than was required, so I uninstalled that (by deleting the application) and went back to the installer, which did a new scan and offered the latest available version, but left the checkbox unselectable - there was no way to get it to install any version of VirtualBox, and no error message given. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4449) DevSuite Installer won't install VirtualBox on Mac

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4449?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4449: ------------------------------ Story Points: 2 Sprint: devex #134 Jun 2017 > DevSuite Installer won't install VirtualBox on Mac > -------------------------------------------------- > > Key: JBDS-4449 > URL: https://issues.jboss.org/browse/JBDS-4449 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac OSX, 10.12.5 > Reporter: Bob Davis > Assignee: Jan Richter > Fix For: 11.0.0.AM2 > > > Installer detected an older version of Virtual box than was required, so I uninstalled that (by deleting the application) and went back to the installer, which did a new scan and offered the latest available version, but left the checkbox unselectable - there was no way to get it to install any version of VirtualBox, and no error message given. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22417) Eclipse will not run with java9 - NoClassDefFoundError

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22417?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22417: --------------------------------------- According to the last comment in the BZ, the fixes that were targeted for Oxygen M7 were reverted in Oxygen RC3: {quote} FYI : All changes made as part of this and bug 516143 to enable launching with Java 9 as well as Java 8 using the same configuration in eclipse.ini have been reverted in Oxygen RC3 via bug 517507 and bug 517482. {quote} So it means that it's still not working now and we'll have to wait for Oxygen.1? [~nickboldt], do I understand this correctly? > Eclipse will not run with java9 - NoClassDefFoundError > ------------------------------------------------------ > > Key: JBIDE-22417 > URL: https://issues.jboss.org/browse/JBIDE-22417 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Martin Malina > Assignee: Jeff MAURY > Priority: Critical > Labels: java9 > Fix For: 4.5.0.AM2 > > Attachments: e, eclipse.log.20161021-1321.txt > > > As of the latest build of Oracle JDK 9, Eclipse Neon M7 will not start. > Java version: > {code} > $ java -version > java version "9-ea" > Java(TM) SE Runtime Environment (build 9-ea+118) > Java HotSpot(TM) 64-Bit Server VM (build 9-ea+118, mixed mode) > {code} > Error log: > {code} > !ENTRY org.eclipse.osgi 4 0 2016-05-19 11:14:42.241 > !MESSAGE Application error > !STACK 1 > org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:626) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:531) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151) > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375) > ... 22 more > Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419) > ... 24 more > !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-05-19 11:14:42.248 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > java.lang.NoClassDefFoundError: javax/annotation/PreDestroy > at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426) > at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154) > at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111) > at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74) > at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:175) > at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106) > at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139) > at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213) > at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120) > at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112) > at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156) > at org.eclipse.osgi.container.Module.publishEvent(Module.java:476) > at org.eclipse.osgi.container.Module.doStop(Module.java:634) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:191) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) > at java.lang.Thread.run(java.base@9-ea/Thread.java:804) > Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419) > ... 21 more > {code} > Upstream issue - targeted for Neon.1: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24317) Analyze capabilities replacement

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24317?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-24317. ------------------------------------ nothing for QE to verify here. Closing. > Analyze capabilities replacement > -------------------------------- > > Key: JBIDE-24317 > URL: https://issues.jboss.org/browse/JBIDE-24317 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > > Analyze how the capabilities features can be replaced when switching to the fabric8 client -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24497) Refactor devstudio-byoe and devstudio-ui-central tests

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24497?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24497: --------------------------------- Story Points: 3 (was: 15) > Refactor devstudio-byoe and devstudio-ui-central tests > ------------------------------------------------------ > > Key: JBIDE-24497 > URL: https://issues.jboss.org/browse/JBIDE-24497 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.0.AM2 > > > There is code repetition in devstudio-byoe and devstudio-ui-central and tests are not stable enough. They should be able to deal with remediation page and all other troubles they can meet during installation. All troubles (if any) should be logged, not ignored. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017