[JBoss JIRA] (JBIDE-26139) openshift does not compile anymore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26139?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26139:
-------------------------------------
Description:
Since a change in the target platform, jbosstools openshift does not compile anymore. an unknown method is used in org.jboss.tools.openshift.egit.test
{code}
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.1.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure:
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift-Pull-Request/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[477]
[ERROR] Ref ref = repository.getRef(Constants.HEAD);
[ERROR] ^^^^^^
[ERROR] The method getRef(String) is undefined for the type Repository
[ERROR] 1 problem (1 error)
[ERROR] -> [Help 1]
{code}
was:Since a change in the target platform, jbosstools openshift does not compile anymore. an unknown method is used in org.jboss.tools.openshift.egit.test
> openshift does not compile anymore
> ----------------------------------
>
> Key: JBIDE-26139
> URL: https://issues.jboss.org/browse/JBIDE-26139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Fix For: 4.6.0.Final
>
>
> Since a change in the target platform, jbosstools openshift does not compile anymore. an unknown method is used in org.jboss.tools.openshift.egit.test
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.1.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift-Pull-Request/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[477]
> [ERROR] Ref ref = repository.getRef(Constants.HEAD);
> [ERROR] ^^^^^^
> [ERROR] The method getRef(String) is undefined for the type Repository
> [ERROR] 1 problem (1 error)
> [ERROR] -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26139) openshift does not compile anymore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26139?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26139:
------------------------------------------
TestRepository marked #getRef as deprecated and tells users to use #extractRef instead
> openshift does not compile anymore
> ----------------------------------
>
> Key: JBIDE-26139
> URL: https://issues.jboss.org/browse/JBIDE-26139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Fix For: 4.6.0.Final
>
>
> Since a change in the target platform, jbosstools openshift does not compile anymore. an unknown method is used in org.jboss.tools.openshift.egit.test
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.1.0:compile (default-compile) on project org.jboss.tools.openshift.egit.test: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift-Pull-Request/tests/org.jboss.tools.openshift.egit.test/src/org/jboss/tools/openshift/egit/internal/test/util/TestRepository.java:[477]
> [ERROR] Ref ref = repository.getRef(Constants.HEAD);
> [ERROR] ^^^^^^
> [ERROR] The method getRef(String) is undefined for the type Repository
> [ERROR] 1 problem (1 error)
> [ERROR] -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25000:
-------------------------------------
Sprint: devex #138 September 2017, devex #151 June 2018 (was: devex #138 September 2017)
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.Final
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> 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.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25000:
-------------------------------------
Fix Version/s: 4.6.0.Final
(was: 4.6.x)
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.Final
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> 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.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25546) Explorer: context menu has "Delete Resource" available even if there's nothing selected
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25546?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25546:
-------------------------------------
Sprint: devex #151 June 2018
> Explorer: context menu has "Delete Resource" available even if there's nothing selected
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-25546
> URL: https://issues.jboss.org/browse/JBIDE-25546
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: explorer
> Fix For: 4.6.0.Final
>
> Attachments: explorer-context-menu.png
>
>
> # ASSERT: have Properties view visible
> # ASSERT: have nothing selected in OpenShift Explorer
> # EXEC: open the context menu in OpenShift Explorer
> Result:
> !explorer-context-menu.png!
> The context menu in OpenShift Explorer holds New > Connection which is right, but also a "Delete Resource" entry which makes no sense at all
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25546) Explorer: context menu has "Delete Resource" available even if there's nothing selected
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25546?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25546:
-------------------------------------
Fix Version/s: 4.6.0.Final
(was: 4.6.x)
> Explorer: context menu has "Delete Resource" available even if there's nothing selected
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-25546
> URL: https://issues.jboss.org/browse/JBIDE-25546
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: explorer
> Fix For: 4.6.0.Final
>
> Attachments: explorer-context-menu.png
>
>
> # ASSERT: have Properties view visible
> # ASSERT: have nothing selected in OpenShift Explorer
> # EXEC: open the context menu in OpenShift Explorer
> Result:
> !explorer-context-menu.png!
> The context menu in OpenShift Explorer holds New > Connection which is right, but also a "Delete Resource" entry which makes no sense at all
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25546) Explorer: context menu has "Delete Resource" available even if there's nothing selected
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25546?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25546:
----------------------------------------
Assignee: Andre Dietisheim
> Explorer: context menu has "Delete Resource" available even if there's nothing selected
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-25546
> URL: https://issues.jboss.org/browse/JBIDE-25546
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: explorer
> Fix For: 4.6.0.Final
>
> Attachments: explorer-context-menu.png
>
>
> # ASSERT: have Properties view visible
> # ASSERT: have nothing selected in OpenShift Explorer
> # EXEC: open the context menu in OpenShift Explorer
> Result:
> !explorer-context-menu.png!
> The context menu in OpenShift Explorer holds New > Connection which is right, but also a "Delete Resource" entry which makes no sense at all
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26078) Properties: edit resource context menu is erroneously labeled "Resources..." (missing "Edit")
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26078?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-26078.
--------------------------------------
Resolution: Done
> Properties: edit resource context menu is erroneously labeled "Resources..." (missing "Edit")
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-26078
> URL: https://issues.jboss.org/browse/JBIDE-26078
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: edit_resource_editor, properties
> Fix For: 4.6.0.Final
>
> Attachments: edit-resource-command.png, image-2018-06-04-15-56-08-882.png
>
>
> steps:
> # ASSERT: have a resource on OpenShift (buildconfig, deplyoment config, build, etc.)
> # ASSERT: have "Properties" view opened
> # EXEC: in explorer: select the project that contains the resource
> # EXEC: in "Properties" view: have the tab selected that contains your resource, select the resource and open up the context menu
> Result:
> !image-2018-06-04-15-56-08-882.png!
> The entry for editing the resource is labeled "Resource...", it should be labeled "Edit Resource..." or be in the submenu "Edit" like it is in OpenShift explorer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26117:
-------------------------------------
Summary: Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui) (was: Connection Wizard: Parse Login command (that was created in clipboard by the web-ui))
> Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-26117
> URL: https://issues.jboss.org/browse/JBIDE-26117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Josef Kopriva
> Labels: connection_wizard
> Fix For: 4.6.x
>
>
> The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi...
> Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection:
> The Eclipse
> There could be a button for parsing login command in clipboard.
> Steps:
> 1. User logins in web browser in OpenShift Console.
> 2. User clicks on "Copy Login Command"
> 3. In OpenShift tooling there could be button for parse login command from clipboard.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months