[JBoss JIRA] (JBIDE-22152) Server Adapter, Debugging: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22152:
------------------------------------------
merged into master
> Server Adapter, Debugging: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: debugging, openshift_v3, server_adapter
> Fix For: 4.4.1.AM1
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png, terminated-launch-entry.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22152) Server Adapter, Debugging: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22152:
-------------------------------------
Fix Version/s: 4.4.1.AM1
(was: 4.4.x)
> Server Adapter, Debugging: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: debugging, openshift_v3, server_adapter
> Fix For: 4.4.1.AM1
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png, terminated-launch-entry.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22152) Server Adapter, Debugging: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22152:
-------------------------------------
Attachment: terminated-launch-entry.png
> Server Adapter, Debugging: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: debugging, openshift_v3, server_adapter
> Fix For: 4.4.x
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png, terminated-launch-entry.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22152) Server Adapter, Debugging: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22152:
------------------------------------------
With the PR the entry now turns <terminated> and then can be removed via context-menu.
!terminated-launch-entry.png!
> Server Adapter, Debugging: Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: debugging, openshift_v3, server_adapter
> Fix For: 4.4.x
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22683) OpenShift Explorer: Manage project context menu item is missing in context menu of a connection
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22683:
-------------------------------------
Summary: OpenShift Explorer: Manage project context menu item is missing in context menu of a connection
Key: JBIDE-22683
URL: https://issues.jboss.org/browse/JBIDE-22683
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM1
Reporter: Marián Labuda
I have not spotted any JIRA related to this so I guess it's a bug. We had a context menu item for managing projects in context menu of an OpenShift 3 connection. Now in nightly build of devstudio 10.0.1.AM1 I don't have this context menu item anymore in the context menu of a connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22642) ProcessInformationStore.loadprocessStore doesn't work on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22642?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22642.
---------------------------------
I tried the original workflow from JBIDE-20729 that triggered the error in JBT 4.4 and Neon and it's no longer happening:
{quote}
I ran Eclipse using "eclipse -consoleLog" from command line, then downloaded and installed WildFly 9.0.2 and then right-clicked the server.
{quote}
Closing.
> ProcessInformationStore.loadprocessStore doesn't work on Windows
> ----------------------------------------------------------------
>
> Key: JBIDE-22642
> URL: https://issues.jboss.org/browse/JBIDE-22642
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.1.Final
> Environment: Windows
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.0.Final
>
>
> - l.90 it searches for a jps file although the file is jps.exe on Windows
> jps = jHomePath.removeLastSegments(1).append("bin").append("jps").toFile();
> error log:
> {noformat}
> java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at java.lang.Runtime.exec(Runtime.java:485)
> at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102)
> at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
> at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
> at java.lang.ProcessImpl.start(ProcessImpl.java:137)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-22653:
----------------------------------
Assignee: (was: Jeff MAURY)
> Can't scale pods down to 0
> --------------------------
>
> Key: JBIDE-22653
> URL: https://issues.jboss.org/browse/JBIDE-22653
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Labels: explorer, openshift_v3
> Fix For: 4.4.1.AM2
>
>
> The scale to... menu lets you scale to any number of replicas, but you can't go down to 0.
> The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment."
> My take is we should have the same behavior in eclipse
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22653:
-------------------------------
Sprint: (was: devex #117 July 2016)
> Can't scale pods down to 0
> --------------------------
>
> Key: JBIDE-22653
> URL: https://issues.jboss.org/browse/JBIDE-22653
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Fred Bricon
> Labels: explorer, openshift_v3
> Fix For: 4.4.1.AM2
>
>
> The scale to... menu lets you scale to any number of replicas, but you can't go down to 0.
> The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment."
> My take is we should have the same behavior in eclipse
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months