[JBoss JIRA] (JBIDE-21899) Wrong service is preselected when creating a new OS3 server adapter from context menu of a service
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21899?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21899:
----------------------------------------
[~scabanovich] could you help with this one?
> Wrong service is preselected when creating a new OS3 server adapter from context menu of a service
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21899
> URL: https://issues.jboss.org/browse/JBIDE-21899
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: openshift_v3, server_adapter_wizard
>
> When I am creating a new OpenShift 3 server adapter from context menu of a service in OpenShift explorer view and I am having several projects and at least 2 same services (names must be equal) in different projects, then in New OS 3 Server Wizard is wrong service. This is happening when I am trying to create a server adapter from context menu of a service which is lower (in order of tree items under an OpenShift 3 connection) then a service with same name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3676) BrowserSim cannot start on openjdk (windows)
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-3676?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk updated JBDS-3676:
------------------------------
Fix Version/s: 9.1.0.GA
> BrowserSim cannot start on openjdk (windows)
> --------------------------------------------
>
> Key: JBDS-3676
> URL: https://issues.jboss.org/browse/JBDS-3676
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Ilya Buziuk
> Labels: havoc, openjdk
> Fix For: 9.1.0.GA
>
>
> Running JBDS on Azul OpenJDK 8, Windows 10.
> Starting BrowserSim fails with the following error:
> {noformat}
> BrowserSim has failed to start with the following error:
> "To use BrowserSim please install Safari or run BrowserSim with Oracle Java 7u7 and higher."
> Also see BrowserSim FAQ.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21905) Server adapter states don't reflect any real state
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21905?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21905.
---------------------------------
Resolution: Done
There are a number of issues with this, but I've done my best to make sure the state matches as best as expected. The fact is that the openshift server adapter actually won't start or stop the openshift service, and is primarily used to control other parts of WTP, such as whether auto-publish is enabled.
I've tried to ensure that when the user starts the server, we at least try to access the service, and so we don't end up with a failure and still have the server in state 'started'.
However, state 'stopped' will probably never be accurate. Our initial suggestion was to not even allow the user to stop the server at all (even just cosmetically), but it turns out being able to 'stop' it was a requirement for our remote debugger logic.
Hopefully the new logic will be more to your liking.
> Server adapter states don't reflect any real state
> --------------------------------------------------
>
> Key: JBIDE-21905
> URL: https://issues.jboss.org/browse/JBIDE-21905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> Having OS server adapters showing started/stopped states is quite perplexing, because they are completely arbitrary.
> For example, I can click start on a stopped server with no connection, then just cancel the connection dialog - it throws an error, but it proceeds to started state anyway.
> It is meaningless to have different states, when their only function is to predend the server is in some state. Plus it introduces steps like the 'stop server before deleting' dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years