[JBoss JIRA] (JBIDE-21614) OpenShift connection is not created when CDK server starts on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21614?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21614:
-----------------------------------
Priority: Critical (was: Major)
> OpenShift connection is not created when CDK server starts on Windows
> ---------------------------------------------------------------------
>
> Key: JBIDE-21614
> URL: https://issues.jboss.org/browse/JBIDE-21614
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Priority: Critical
>
> I'm testing the latest JBDS 9.1.0.CR1 nightly build + CDK from the PDK installer.
> When I create and start CDK server on my Ubuntu it creates OpenShift connection.
> When I do the same (same CDK, same JBDS build) on Windows, vargrant starts successfully (I can access OS web console etc.) but the OpenShift connection is not created in JBDS.
> It worked before (sometime ago on a different installation).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71
by Omair Majid (JIRA)
[ https://issues.jboss.org/browse/JBDS-3586?page=com.atlassian.jira.plugin.... ]
Omair Majid commented on JBDS-3586:
-----------------------------------
Thanks Andrej! I can reproduce the bug. I left a few comments on the eclipse bug.
> Cannot install Integration Stack from central with: OpenJDK-1.8.0.65, OpenJDK-1.8.0.71
> --------------------------------------------------------------------------------------
>
> Key: JBDS-3586
> URL: https://issues.jboss.org/browse/JBDS-3586
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, updatesite
> Affects Versions: 9.1.0.Beta2
> Reporter: Jan Richter
> Priority: Critical
>
> Trying to install IS from central early access, I'm getting the following error:
> {noformat}
> An error occurred while collecting items to be installed
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354.
> Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21613) NPE if click on failed CDK server
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-21613:
--------------------------------------
Summary: NPE if click on failed CDK server
Key: JBIDE-21613
URL: https://issues.jboss.org/browse/JBIDE-21613
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.3.1.CR1
Reporter: Alexey Kazakov
I ran my CDK server but it failed by timeout (it tool longer than the timeout to start the server).
When the server finally started (I saw it in the console) I clicked on the server in the server view to "restart" it. You don't need to start/stop the server. Just click on/select the server in the view:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53)
at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111)
at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188)
at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203)
at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2178)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1717)
at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1069)
at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:368)
at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:383)
at org.eclipse.wst.server.ui.internal.cnf.ServerDecoratorsHandler$1.run(ServerDecoratorsHandler.java:58)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1023)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:651)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
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 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:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21598) OpenShift resource tab properties are shrinked in case of small view
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21598?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21598:
-----------------------------------------------
It is implementation of TabbedPropertyList in TabbedPropertySheetPage that cannot be customized, it only can be replaced with entirely custom sheet page implementation.
> OpenShift resource tab properties are shrinked in case of small view
> --------------------------------------------------------------------
>
> Key: JBIDE-21598
> URL: https://issues.jboss.org/browse/JBIDE-21598
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: openshift_v3
> Attachments: shrinked_tabbed_props.png
>
>
> In properties view when browsing OpenShift resources (e.g. project in OpenShift explorer is selected and properties view is opened) and properties view is too small (height - y axis), the tabbed properties are shrinked and it is necessary to click button on top/bottom of them to get to other tabbed properties representing OpenShift resources. See following screenshot
> !shrinked_tabbed_props.png!"
> This is usability issues because it is pain to click all the time instead of scrolling (suggested solution would be to have a scroll bar) and it causes problem for automatized tests when working with widgets.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months