[JBoss JIRA] (JBIDE-22003) Order of project in New OS3 Server Adapter wizard could be better
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22003?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-22003:
----------------------------------------
Assignee: Viacheslav Kabanovich (was: Andre Dietisheim)
Resolution: Done
> Order of project in New OS3 Server Adapter wizard could be better
> -----------------------------------------------------------------
>
> Key: JBIDE-22003
> URL: https://issues.jboss.org/browse/JBIDE-22003
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.CR1
>
>
> With latest changes to New OS3 Server Adapter wizard the current order of projects, listed on wizard page where service selection is done, is a bit strange. At first there are alphanumeric ordered projects with no services and therefore they are not useful for creation of a new OS3 Server Adapter and then there are projects with any service ordered in alphanumberic order. It results in following.
> Assume project aproject with no services, bproject with a service, c project with no services, d project with a service. Order on the wizard page is following:
> a
> c
> b
> d
> I think we are safe not to list projects with no services there or otherwise we should keep alphanumeric order regardless existence of a service under a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22003) Order of project in New OS3 Server Adapter wizard could be better
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-22003:
----------------------------------------
Summary: Order of project in New OS3 Server Adapter wizard could be better
Key: JBIDE-22003
URL: https://issues.jboss.org/browse/JBIDE-22003
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Fix For: 4.4.0.Alpha1
With latest changes to New OS3 Server Adapter wizard the current order of projects, listed on wizard page where service selection is done, is a bit strange. At first there are alphanumeric ordered projects with no services and therefore they are not useful for creation of a new OS3 Server Adapter and then there are projects with any service ordered in alphanumberic order. It results in following.
Assume project aproject with no services, bproject with a service, c project with no services, d project with a service. Order on the wizard page is following:
a
c
b
d
I think we are safe not to list projects with no services there or otherwise we should keep alphanumeric order regardless existence of a service under a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21996) Order of project in New OS3 Server Adapter wizard could be better
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21996?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21996:
------------------------------------------
merged into master
> Order of project in New OS3 Server Adapter wizard could be better
> -----------------------------------------------------------------
>
> Key: JBIDE-21996
> URL: https://issues.jboss.org/browse/JBIDE-21996
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
>
> With latest changes to New OS3 Server Adapter wizard the current order of projects, listed on wizard page where service selection is done, is a bit strange. At first there are alphanumeric ordered projects with no services and therefore they are not useful for creation of a new OS3 Server Adapter and then there are projects with any service ordered in alphanumberic order. It results in following.
> Assume project aproject with no services, bproject with a service, c project with no services, d project with a service. Order on the wizard page is following:
> a
> c
> b
> d
> I think we are safe not to list projects with no services there or otherwise we should keep alphanumeric order regardless existence of a service under a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21996) Order of project in New OS3 Server Adapter wizard could be better
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21996?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21996:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
> Order of project in New OS3 Server Adapter wizard could be better
> -----------------------------------------------------------------
>
> Key: JBIDE-21996
> URL: https://issues.jboss.org/browse/JBIDE-21996
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
>
> With latest changes to New OS3 Server Adapter wizard the current order of projects, listed on wizard page where service selection is done, is a bit strange. At first there are alphanumeric ordered projects with no services and therefore they are not useful for creation of a new OS3 Server Adapter and then there are projects with any service ordered in alphanumberic order. It results in following.
> Assume project aproject with no services, bproject with a service, c project with no services, d project with a service. Order on the wizard page is following:
> a
> c
> b
> d
> I think we are safe not to list projects with no services there or otherwise we should keep alphanumeric order regardless existence of a service under a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-620) Fix Guides Test
by Matej Kralik (JIRA)
Matej Kralik created JBTIS-620:
----------------------------------
Summary: Fix Guides Test
Key: JBTIS-620
URL: https://issues.jboss.org/browse/JBTIS-620
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, teiid
Affects Versions: 4.3.0.Beta1, 4.2.5.Final
Reporter: Matej Kralik
Assignee: Matej Kralik
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22002) Connecting to a OS 3 Server adapter on restarted Eclipse throws error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22002?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22002:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Connecting to a OS 3 Server adapter on restarted Eclipse throws error
> ---------------------------------------------------------------------
>
> Key: JBIDE-22002
> URL: https://issues.jboss.org/browse/JBIDE-22002
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up and server is still stopped. Following attempt to start the server adapter finish successfully (it is because connection is already established, but in first attempt although I was prompted to fill in credentials and connection was some time during the process established, it seems the server adapter was not able to comprehend it.
> {code}
> The OpenShift service for server eap-app at OpenShift 3 (10.3.2.2) could not be reached.
> com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication.
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:287)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:276)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.pollState(OpenShiftLaunchController.java:73)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:56)
> 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:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22002) Connecting to a OS 3 Server adapter on restarted Eclipse throws error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22002?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22002:
------------------------------------------
cherry-picked into master
> Connecting to a OS 3 Server adapter on restarted Eclipse throws error
> ---------------------------------------------------------------------
>
> Key: JBIDE-22002
> URL: https://issues.jboss.org/browse/JBIDE-22002
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up and server is still stopped. Following attempt to start the server adapter finish successfully (it is because connection is already established, but in first attempt although I was prompted to fill in credentials and connection was some time during the process established, it seems the server adapter was not able to comprehend it.
> {code}
> The OpenShift service for server eap-app at OpenShift 3 (10.3.2.2) could not be reached.
> com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication.
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:287)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:276)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.pollState(OpenShiftLaunchController.java:73)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:56)
> 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:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21902) Connecting to a OS 3 Server adapter on restarted Eclipse throws error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21902?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21902:
-------------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> Connecting to a OS 3 Server adapter on restarted Eclipse throws error
> ---------------------------------------------------------------------
>
> Key: JBIDE-21902
> URL: https://issues.jboss.org/browse/JBIDE-21902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up and server is still stopped. Following attempt to start the server adapter finish successfully (it is because connection is already established, but in first attempt although I was prompted to fill in credentials and connection was some time during the process established, it seems the server adapter was not able to comprehend it.
> {code}
> The OpenShift service for server eap-app at OpenShift 3 (10.3.2.2) could not be reached.
> com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication.
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:287)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:276)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.pollState(OpenShiftLaunchController.java:73)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:56)
> 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:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21902) Connecting to a OS 3 Server adapter on restarted Eclipse throws error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21902?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21902:
------------------------------------------
merged into jbosstools-4.3.x
> Connecting to a OS 3 Server adapter on restarted Eclipse throws error
> ---------------------------------------------------------------------
>
> Key: JBIDE-21902
> URL: https://issues.jboss.org/browse/JBIDE-21902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up and server is still stopped. Following attempt to start the server adapter finish successfully (it is because connection is already established, but in first attempt although I was prompted to fill in credentials and connection was some time during the process established, it seems the server adapter was not able to comprehend it.
> {code}
> The OpenShift service for server eap-app at OpenShift 3 (10.3.2.2) could not be reached.
> com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication.
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:287)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:276)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.pollState(OpenShiftLaunchController.java:73)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:56)
> 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:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years