[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22361:
----------------------------------
Priority: Critical (was: Major)
> OpenShift Explorer: Watcher does not work
> -----------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Service is collapsed, sometimes even several times. Upon expanding an existing service it still contains old pod (either application on build pod). So once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Application pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22361:
----------------------------------
Labels: explorer (was: )
> OpenShift Explorer: Watcher does not work
> -----------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Service is collapsed, sometimes even several times. Upon expanding an existing service it still contains old pod (either application on build pod). So once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Application pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22361) OpenShift Explorer: Watcher does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22361?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22361:
----------------------------------
Labels: explorer openshift_v3 (was: explorer)
> OpenShift Explorer: Watcher does not work
> -----------------------------------------
>
> Key: JBIDE-22361
> URL: https://issues.jboss.org/browse/JBIDE-22361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Priority: Critical
> Labels: explorer, openshift_v3
>
> When I am trying to create a new application based on eap 6.4 template and I am having only one project in OpenShift Explorer view, watcher does not work. Service is collapsed, sometimes even several times. Upon expanding an existing service it still contains old pod (either application on build pod). So once I create a new EAP 6.4 application there is eap-app-1-build pod all the time in running state. Application pod is visible only upon refresh of a project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22360) Extract OAuth token from the New Connection wizard
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-22360:
----------------------------------
Summary: Extract OAuth token from the New Connection wizard
Key: JBIDE-22360
URL: https://issues.jboss.org/browse/JBIDE-22360
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Jeff MAURY
Priority: Minor
Fix For: 4.4.x
When creating a new connection in OAuth mode, the user can use an integrated browser to connect to Openshift and once connected, the page displays the token. We could extract the token from that page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBTIS-320) Remove Savara from the Integration Stack community capture
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-320?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-320.
-----------------------------------
Savara was removed in JBTIS 4.1.7.Final, so I'm closing this issue
> Remove Savara from the Integration Stack community capture
> ----------------------------------------------------------
>
> Key: JBTIS-320
> URL: https://issues.jboss.org/browse/JBTIS-320
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: savara
> Affects Versions: 4.1.6.Final, 4.2.0.Final
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.2.0.Final
>
>
> Gary Brown has requested that Savara be removed from the Kepler and Luna captures of the community IS:
> Hi Paul
> Would you be able to remove savara from the JDT and IS (if still in there) configurations as the current version is no longer going to be supported?
> Some of the concepts may get included in Overlord, or a possible future version of savara, but at the moment it is unclear, so we think it is better to leave the current plugins out of any distribution.
> Regards
> Gary
> Note: Savara is not part of the production (JBDSIS) build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months