[JBoss JIRA] (JBIDE-13565) NPE When selected multiple OpenShift server adapters
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13565?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13565:
------------------------------------------
@Stefan: I cannot reproduce your issue here. I agree on the fact that port forwarding should be disabled if you select 2 server adapters. Nevertheless I did not get an error. The first selected adapter was used and the port forwarding dialog showed up (the app was stopped in my case, thus the error in the dialog):
!first-adapter-is-used.png!
What am I missing?
> NPE When selected multiple OpenShift server adapters
> ----------------------------------------------------
>
> Key: JBIDE-13565
> URL: https://issues.jboss.org/browse/JBIDE-13565
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha2
>
> Attachments: first-adapter-is-used.png
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13843) SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13843:
------------------------------------
[~ldimaggio] or [~mmalina] Are you satisfied with the fact that we've moved up to SWTBot 2.1 and JUnit 4.11? If so, please close this ticket. If not, please explain what needs to be done to make you happy here. :D
> SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13843
> URL: https://issues.jboss.org/browse/JBIDE-13843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, testing-tools
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 4.1.0.Alpha2
>
>
> Eclipse 4.3M5a contains:
> {code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code}
> But in Eclipse 4.3M6, the only JUnit available is:
> {code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code}
> So, we need to see if a newer SWTBot can be used which depends on org.junit instead of org.junit4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13922) OpenShift "Secure Storage" diaglog in infinit loop of prompting
by R Searls (JIRA)
R Searls created JBIDE-13922:
--------------------------------
Summary: OpenShift "Secure Storage" diaglog in infinit loop of prompting
Key: JBIDE-13922
URL: https://issues.jboss.org/browse/JBIDE-13922
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Environment: Fedora 18
Reporter: R Searls
Assignee: Andre Dietisheim
Running : JBoss Developer Studio
version:6.0.1.GA
Build id:GA-v20130327-2052-B361
OS: Fedora 18
When creating a new OpenShift App in the "New OpenShift Application" dialog
I type in my password, (I have an existing account.) and select the checkbox,
"Save password (could trigger storage login)" and click next. The " Secure
Storage" dialog displays. I click the cancel button. Each time I click cancel
in this dialog, the dialog closes and pops back open. It's in an infinit loop.
I must kill the app to get out of this cycle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13659) OpenShift Server wizard is giving different name to server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13659?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13659:
------------------------------------------
@Stefan: reading your issue it looks like it's "only" the name of the adapter that's wrong. In this case this would be just minor. Wrong?
> OpenShift Server wizard is giving different name to server adapter
> ------------------------------------------------------------------
>
> Key: JBIDE-13659
> URL: https://issues.jboss.org/browse/JBIDE-13659
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.0.Alpha2
>
> Attachments: out.ogv
>
>
> Trying to create server adapter for application *spring* and server wizard uses a different name for the server adapter (actually from different accout): see [^out.ogv]
> No entry in error log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-11881) Display application state in OpenShift Explorer and Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11881:
-------------------------------------
Fix Version/s: 4.1.0.Beta1
(was: 4.1.0.Alpha2)
> Display application state in OpenShift Explorer and Properties view
> -------------------------------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta1
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years