[JBoss JIRA] (JBIDE-24583) Cannot run CDK 2.3
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24583?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24583.
---------------------------------
> Cannot run CDK 2.3
> ------------------
>
> Key: JBIDE-24583
> URL: https://issues.jboss.org/browse/JBIDE-24583
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.AM1
> Environment: DevStudio 11.0.0.AM1
> CDK 2.3
> Fedora 25
> Oracle JDK 1.8
> Reporter: Tomáš Sedmík
> Fix For: 4.5.0.Final
>
> Attachments: cdk-start-error.mp4
>
>
> I'm unable to run CDK 2.3 in DevStudio 11.0.0.AM1 (see attached video).
> {code}
> null
> org.eclipse.core.jobs
> Error
> Tue Jun 27 18:41:40 CEST 2017
> An internal error occurred during: "Starting CDK 2.3".
> java.lang.NoClassDefFoundError: com/openshift/restclient/OpenShiftException
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.getCDKPoller(CDKLaunchController.java:257)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:151)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.lang.ClassNotFoundException: com.openshift.restclient.OpenShiftException cannot be found by org.jboss.tools.openshift.cdk.server_3.4.0.v20170530-1720
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 10 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24885) Tycho tests are not working properly
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24885?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-24885:
--------------------------------------
Description:
The following dependency
{code}
<dependency>
<type>eclipse-feature</type>
<artifactId>org.eclipse.e4.rcp</artifactId>
<version>0.0.0</version>
</dependency>
{code}
was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some *org.eclipse.jdt.core* issues. By adding the dependency the test work properly.
was:
The following dependency
{code}
<dependency>
<type>eclipse-feature</type>
<artifactId>org.eclipse.e4.rcp</artifactId>
<version>0.0.0</version>
</dependency>
{code}
was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some org.eclipse.jdt.core.issues. By adding the dependency the test work properly.
> Tycho tests are not working properly
> ------------------------------------
>
> Key: JBIDE-24885
> URL: https://issues.jboss.org/browse/JBIDE-24885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.1.AM1
> Reporter: Andrej Podhradsky
> Attachments: errorLog.txt
>
>
> The following dependency
> {code}
> <dependency>
> <type>eclipse-feature</type>
> <artifactId>org.eclipse.e4.rcp</artifactId>
> <version>0.0.0</version>
> </dependency>
> {code}
> was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some *org.eclipse.jdt.core* issues. By adding the dependency the test work properly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24885) Tycho tests are not working properly
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24885?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-24885:
--------------------------------------
Attachment: errorLog.txt
> Tycho tests are not working properly
> ------------------------------------
>
> Key: JBIDE-24885
> URL: https://issues.jboss.org/browse/JBIDE-24885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.1.AM1
> Reporter: Andrej Podhradsky
> Attachments: errorLog.txt
>
>
> The following dependency
> {code}
> <dependency>
> <type>eclipse-feature</type>
> <artifactId>org.eclipse.e4.rcp</artifactId>
> <version>0.0.0</version>
> </dependency>
> {code}
> was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some *org.eclipse.jdt.core* issues. By adding the dependency the test work properly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24885) Tycho tests are not working properly
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBIDE-24885:
-----------------------------------------
Summary: Tycho tests are not working properly
Key: JBIDE-24885
URL: https://issues.jboss.org/browse/JBIDE-24885
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.5.1.AM1
Reporter: Andrej Podhradsky
The following dependency
```
<dependency>
<type>eclipse-feature</type>
<artifactId>org.eclipse.e4.rcp</artifactId>
<version>0.0.0</version>
</dependency>
```
was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some org.eclipse.jdt.core.issues. By adding the dependency the test work properly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24885) Tycho tests are not working properly
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24885?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-24885:
--------------------------------------
Description:
The following dependency
{code}
<dependency>
<type>eclipse-feature</type>
<artifactId>org.eclipse.e4.rcp</artifactId>
<version>0.0.0</version>
</dependency>
{code}
was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some org.eclipse.jdt.core.issues. By adding the dependency the test work properly.
was:
The following dependency
```
<dependency>
<type>eclipse-feature</type>
<artifactId>org.eclipse.e4.rcp</artifactId>
<version>0.0.0</version>
</dependency>
```
was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some org.eclipse.jdt.core.issues. By adding the dependency the test work properly.
> Tycho tests are not working properly
> ------------------------------------
>
> Key: JBIDE-24885
> URL: https://issues.jboss.org/browse/JBIDE-24885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.1.AM1
> Reporter: Andrej Podhradsky
>
> The following dependency
> {code}
> <dependency>
> <type>eclipse-feature</type>
> <artifactId>org.eclipse.e4.rcp</artifactId>
> <version>0.0.0</version>
> </dependency>
> {code}
> was removed in parent pom 4.5.1.AM1-SNAPSHOT and some tests stopped working due to some org.eclipse.jdt.core.issues. By adding the dependency the test work properly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24754) Redhat central screen doesnt show due to JS error
by Robert Kratky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24754?page=com.atlassian.jira.plugi... ]
Robert Kratky commented on JBIDE-24754:
---------------------------------------
[~supriya.bharadwaj], done.
> Redhat central screen doesnt show due to JS error
> -------------------------------------------------
>
> Key: JBIDE-24754
> URL: https://issues.jboss.org/browse/JBIDE-24754
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.5.0.AM1
> Reporter: Anton Hughes
> Assignee: Josef Kopriva
> Fix For: 4.5.x
>
>
> I am trying to run the latest Jboss Tools (Oxygen) on Ubuntu 17.04.
> h2. Eclipse Version
> Eclipse Java EE IDE for Web Developers.
> Version: Oxygen Release (4.7.0)
> Build id: 20170620-1800
> h2. Stacktrace
> {code:java}
> org.eclipse.swt.SWTException: An exception was raised in JavaScript
> at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273)
> at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324)
> at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
> at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175)
> at org.eclipse.ui.forms.editor.FormPage.lambda$0(FormPage.java:163)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:163)
> at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:480)
> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077)
> at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:614)
> at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:106)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1289)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.lambda$0(LazyStackRenderer.java:68)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5439)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> 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.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:437)
> at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:425)
> at org.jboss.tools.central.ShowJBossCentral$2.run(ShowJBossCentral.java:110)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4497)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4110)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24875) Name of cdk 3 adapter is different depending on using detection or adding manually
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24875?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24875.
---------------------------------
[~odockal], I'm pretty sure that's what I requested in this JIRA and that's what Rob did - to use Container Development Environment 3 for cdk 3 server adapter both created via runtime detection and manually. You're right that it's a bit suboptimal to have Container Development Environment (without version number) for cdk2. But this JIRA was only about cdk 3. Feel free to create another jira for cdk 2 if you think it's needed.
Verified in devstudio 11.1 nightly.
> Name of cdk 3 adapter is different depending on using detection or adding manually
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-24875
> URL: https://issues.jboss.org/browse/JBIDE-24875
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM1
>
>
> This is a followup of JBIDE-24447.
> When cdk 3 is auto detected (typically when you start devstudio and ~/.minishift exists), the adapter will be created automatically with the name "Container Development Environment 3". On the other hand, if you choose to create the cdk 3 server adapter manually, the default name is "Container Development Environment". These should be consistent.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months