[JBoss JIRA] (JBDS-4592) Container Development Environment 3.2+ marked as started after minishift failure
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4592?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4592:
--------------------------------
Attachment: image.png
> Container Development Environment 3.2+ marked as started after minishift failure
> ---------------------------------------------------------------------------------
>
> Key: JBDS-4592
> URL: https://issues.jboss.org/browse/JBDS-4592
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, runtime
> Affects Versions: 11.1.0.GA
> Environment: Red Hat JBoss Developer Studio
> Version: 11.1.0.GA
> Build id: GA-v20171023-1808-B1449
> OS: Windows 10, v.10.0, x86_64 / win32
> Reporter: Denis Golovin
> Attachments: image.png
>
>
> Running Latest DevStudio nightly I am getting error during CDK 3.2.0-rc.1 start in server console
> {code}-- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
> -- Minishift VM will be configured with ...
> Memory: 4 GB
> vCPUs : 2
> Disk size: 20 GB
> -- Starting Minishift VM ....................................... OK
> -- Registering machine using subscription-manager
> Registration in progress ................. FAIL [41s]
> Error to register VM: ssh command error:
> command : sudo -E subscription-manager register --auto-attach --username user(a)gmail.com --password 'password'
> err : exit status 70
> output : Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information.
> Registering to: subscription.rhsm.redhat.com:443/subscription
> The system has been registered with ID: e3f3d67d-c835-4f7c-a2e9-ac9d94b9e2ef {code}
> CDK is still marked as started in servers view.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-22417) Eclipse will not run with java9 - NoClassDefFoundError
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22417?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22417:
-------------------------------
Fix Version/s: 4.5.2.AM2
(was: 4.5.x)
> 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.2.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.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18654:
-------------------------------
Description:
Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9.
There is a tool called jdeps that we can use to check for this using the -jdkinternals flag.
https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
The sooner the better we get this done as it is feedback to the Java 9 team.
If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins.
was:
Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9.
There is a tool called jdeps that we can use to check for this using the -jdkinternals flag.
https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
The sooner the better we get this done as it is feedback to the Java 9 team.
If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins.
Fix Version/s: 4.5.2.AM2
(was: 4.5.x)
> run jdeps on our jars to see how dependent we are on api that might go away in Java 9
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18654
> URL: https://issues.jboss.org/browse/JBIDE-18654
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Jeff MAURY
> Fix For: 4.3.x, 4.5.2.AM2
>
>
> Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9.
> There is a tool called jdeps that we can use to check for this using the -jdkinternals flag.
> https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
> The sooner the better we get this done as it is feedback to the Java 9 team.
> If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBDS-4553) Get ready for Java 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4553?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4553:
-----------------------------
Summary: Get ready for Java 9 (was: Get ready for Java9)
Epic Name: Get ready for Java 9
> Get ready for Java 9
> --------------------
>
> Key: JBDS-4553
> URL: https://issues.jboss.org/browse/JBDS-4553
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: installer, platform-installer
> Affects Versions: 11.1.0.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: installer, java9
> Fix For: 11.2.0.AM1
>
>
> When 11.1 will be out, Java9 will also be out. The installer refuses to accept Java9 JVM when JBDS is installed. Shouldn't we accept them now ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBDS-4555) Unknown category error in Red Hat Central - Integration Stack connectors don't show Supported status
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4555?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4555:
-----------------------------
Fix Version/s: 11.1.0.GA
(was: 11.2.0.AM1)
> Unknown category error in Red Hat Central - Integration Stack connectors don't show Supported status
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4555
> URL: https://issues.jboss.org/browse/JBDS-4555
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 11.1.0.AM2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 11.1.0.GA
>
> Attachments: categories.png
>
>
> I installed devstudio 11.1.0.AM2 B1060 and went to central's Updates/Software tab and immediately got these errors:
> Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.switchyard' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar
> Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.soa' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar
> Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.bpr' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_3405701925693823433.jar
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months