[JBoss JIRA] (JBIDE-13303) errors in error log when navigating openshift explorer and no connection setup
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13303?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13303:
------------------------------------------
@Max: The log entry is only created as soon as you select the connection. there's no log entry before, when opening the view initially.
> errors in error log when navigating openshift explorer and no connection setup
> ------------------------------------------------------------------------------
>
> Key: JBIDE-13303
> URL: https://issues.jboss.org/browse/JBIDE-13303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
>
> Open openshift explorer with properties view and no connection open and no network attached.
> com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.UnknownHostException: openshift.redhat.com
> at com.openshift.internal.client.RestService.request(RestService.java:103)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:72)
> at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:135)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:104)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199)
> at org.jboss.tools.openshift.express.internal.ui.property.UserPropertySource$1.run(UserPropertySource.java:112)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.net.UnknownHostException: openshift.redhat.com
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:194)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:99)
> at com.openshift.internal.client.RestService.request(RestService.java:139)
> at com.openshift.internal.client.RestService.request(RestService.java:97)
> ... 9 more
> Caused by: java.net.UnknownHostException: openshift.redhat.com
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> ... 12 more
> Caused by: java.net.UnknownHostException: openshift.redhat.com
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
> at java.net.Socket.connect(Socket.java:529)
> at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
> at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272)
> at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:94)
> ... 11 more
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-13303) errors in error log when navigating openshift explorer and no connection setup
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13303?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13303:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have a connection with password stored (in secured storage) in your OpenShift Explorer
# ASSERT: make sure you have no network
# ASSERT: tail -f your Eclipse logs so that you get what happens in it
# EXEC: launch a fresh Eclipse and open *OpenShift Explorer* & *Properties* view
# EXEC: select your connection in OpenShift Explorer
# ASSERT: secure storage prompts your for the secure storage pw (if you already used secure storage and gave it the pw before, you wont get the prompt)
# EXEC: give secure storage pw
# EXEC: look into your Eclipse log:
Result:
{code}
com.openshift.client.OpenShiftEndpointException: Could not request https://openshift.redhat.com/broker/rest/api: java.net.UnknownHostException: openshift.redhat.com
at com.openshift.internal.client.RestService.request(RestService.java:117)
at com.openshift.internal.client.RestService.request(RestService.java:102)
at com.openshift.internal.client.RestService.request(RestService.java:83)
at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:134)
at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:103)
at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219)
at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199)
at org.jboss.tools.openshift.express.internal.ui.property.UserPropertySource$1.run(UserPropertySource.java:112)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.net.UnknownHostException: openshift.redhat.com
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:213)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:180)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:111)
at com.openshift.internal.client.RestService.request(RestService.java:153)
at com.openshift.internal.client.RestService.request(RestService.java:109)
... 9 more
Caused by: java.net.UnknownHostException: openshift.redhat.com
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491)
at java.security.AccessController.doPrivileged(Native Method)
at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196)
... 13 more
Caused by: java.net.UnknownHostException: openshift.redhat.com
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:559)
at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:395)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:530)
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:178)
... 12 more
{code}
> errors in error log when navigating openshift explorer and no connection setup
> ------------------------------------------------------------------------------
>
> Key: JBIDE-13303
> URL: https://issues.jboss.org/browse/JBIDE-13303
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
>
> Open openshift explorer with properties view and no connection open and no network attached.
> com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.UnknownHostException: openshift.redhat.com
> at com.openshift.internal.client.RestService.request(RestService.java:103)
> at com.openshift.internal.client.RestService.request(RestService.java:91)
> at com.openshift.internal.client.RestService.request(RestService.java:72)
> at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:135)
> at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:104)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219)
> at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199)
> at org.jboss.tools.openshift.express.internal.ui.property.UserPropertySource$1.run(UserPropertySource.java:112)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.net.UnknownHostException: openshift.redhat.com
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:194)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:99)
> at com.openshift.internal.client.RestService.request(RestService.java:139)
> at com.openshift.internal.client.RestService.request(RestService.java:97)
> ... 9 more
> Caused by: java.net.UnknownHostException: openshift.redhat.com
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177)
> ... 12 more
> Caused by: java.net.UnknownHostException: openshift.redhat.com
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
> at java.net.Socket.connect(Socket.java:529)
> at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:158)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
> at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272)
> at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172)
> at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911)
> at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
> at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:94)
> ... 11 more
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2577) JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs
by Pete Muir (JIRA)
[ https://issues.jboss.org/browse/JBDS-2577?page=com.atlassian.jira.plugin.... ]
Pete Muir commented on JBDS-2577:
---------------------------------
I would agree with Kris. What we normally have done is use a build tool to minify js when we do a production build for our own js. And perhaps switch the minfied JS libs on a CDN based on a template that knows whether we are in prod or development.
> JBDS70_0813: [Partial] (Dev) (P1) Support non-minified/minified JS libs
> -----------------------------------------------------------------------
>
> Key: JBDS-2577
> URL: https://issues.jboss.org/browse/JBDS-2577
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Requirements
> Reporter: Jiri Pallich
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 7.0.0.Beta2
>
>
> Support non-minified JS libs for Dev, swap in minified JS libs for production (wro4j - maven integration?).
> Examples of JS libs: jQuery, jQuery Mobile
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14350) Search field disappears when Central editor is too small
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14350?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14350:
---------------------------------------
{quote}
what kind of icon do you have in mind?
{quote}
Whatever you choose. As Max says, you are the master of the design.
If you say it is the best to "keep the checkbox and just hide the label" so who I am to comment on that. :)
> Search field disappears when Central editor is too small
> --------------------------------------------------------
>
> Key: JBIDE-14350
> URL: https://issues.jboss.org/browse/JBIDE-14350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha2
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
> Attachments: searchField.png, searchField1.png
>
>
> Search field disappears, when Central editor is shrinked to certain width.
> Would it be possible either move the search field under buttons and "show on startup" checkbox or define some minimal width.
> Thanks
> !searchField.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
12 years, 11 months
[JBoss JIRA] (JBIDE-14334) Double click/open With... for cheatsheet viewer
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14334?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14334:
---------------------------------------
Cheat Sheets is a view, not an editor so it isn't easy to override the default double-click action in the Package Explore view.
I have succeeded to do it in the Project Explorer view because it is a Common Navigator view.
The Package Explorer view uses a hardcoded OpenAction class. Maybe it is possible to replace its action set, but, I think, it would be easier and more reliable to add a new action to the context menu (Open in the Cheat Sheets view) that would be visible for all cheatsheet files in all views. Double-click will open a cheatsheet in an editor and this action would open a cheatsheet in the Cheat Sheets view.
> Double click/open With... for cheatsheet viewer
> -----------------------------------------------
>
> Key: JBIDE-14334
> URL: https://issues.jboss.org/browse/JBIDE-14334
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples
> Reporter: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
>
> right now it is tricky to open a cheatsheet.xml file in the cheatsheet viewer.
> Can we make it the default action for open/edit or at least make it possible to choose as the default action for xml files with cheatsheets in them ?
> maybe do it automatically for .cheatsheet.xml files ?
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14072) Messaging for JPP 6 in JBDS plugin
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14072?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14072:
---------------------------------------
Maybe we could solve the issue using the runtime fix. We could add GateIn, JPP 6.0 (EAP 6.x with the portlet component) to newer quickstarts and exclude it for older examples.
> Messaging for JPP 6 in JBDS plugin
> ----------------------------------
>
> Key: JBIDE-14072
> URL: https://issues.jboss.org/browse/JBIDE-14072
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Portal/GateIn
> Affects Versions: 4.0.2.Final, 4.1.0.Beta1
> Environment: All
> Reporter: Divya Mehra
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
>
> Starting from GateIn 3.5/JPP 6.0, Maven quick starts would be the recommended way to bootstrap a portal project.
> Older technology, for example JSF 1.2 and Rich Faces 3 portlets, would not work if deployed on GateIn 3.5/JPP 6.0 (or later versions).
> It is desirable that we message prominently in the JBDS plugin for portal that the developer should use the quick starts (instead of the plugin) for deployments on GateIn 3.5/JPP 6.0 or later versions.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14333) have context sensitive parameterized commands for open file, show type etc. with proper API
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14333?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14333:
---------------------------------------
{quote}
currently our custom cheatsheet commands requires the project name(s) to be known upfront. We should make them less reliant on project names and if at all possible have the project name calculated based on the project the cheatsheet file is open in.
{quote}
We can find the project name in our custom cheatsheet command if the cheatsheet is placed in the workspace.
Would we replace ${project} with this project name in all parameters?
{quote}
The commands should also actually be commands with named parameters so the order of parameters does not matter and we should make sure these have a good and long term API so cheatsheets will continue to work well in the future.
{quote}
Those parameters have to be named as param1, param2 up to param9, but don't have to be ordered. See http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc....
We could create an upstream feature request.
> have context sensitive parameterized commands for open file, show type etc. with proper API
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-14333
> URL: https://issues.jboss.org/browse/JBIDE-14333
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples
> Reporter: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1, 4.1.0.Beta2
>
>
> currently our custom cheatsheet commands requires the project name(s) to be known upfront. We should make them less reliant on project names and if at all possible have the project name calculated based on the project the cheatsheet file is open in.
> The commands should also actually be commands with named parameters so the order of parameters does not matter and we should make sure these have a good and long term API so cheatsheets will continue to work well in the future.
--
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
12 years, 11 months
[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.Beta2
(was: 4.1.0.Beta1)
> 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.Beta2
>
>
> 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
12 years, 11 months