May 2016 - jbosstools-issues - Jboss List Archives

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-22360) Extract OAuth token from the New Connection wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22360?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22360: ------------------------------- Story Points: 2 > 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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBDS-3875) Split gulpfile.js to multiple modules to simplify maintenance

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3875?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3875: -------------------------------- Story Points: 2 > Split gulpfile.js to multiple modules to simplify maintenance > ------------------------------------------------------------- > > Key: JBDS-3875 > URL: https://issues.jboss.org/browse/JBDS-3875 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Pavol Pitonak > Labels: havoc > Fix For: 10.0.0.Alpha2 > > > Following up from JBDS-3851. Split the gulpfile into separate modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3875) Split gulpfile.js to multiple modules to simplify maintenance

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3875?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3875: -------------------------------- Sprint: devex #114 May 2016 > Split gulpfile.js to multiple modules to simplify maintenance > ------------------------------------------------------------- > > Key: JBDS-3875 > URL: https://issues.jboss.org/browse/JBDS-3875 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Pavol Pitonak > Labels: havoc > Fix For: 10.0.0.Alpha2 > > > Following up from JBDS-3851. Split the gulpfile into separate modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3875) Split gulpfile.js to multiple modules to simplify maintenance

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3875?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3875: -------------------------------- Fix Version/s: 10.0.0.Alpha2 > Split gulpfile.js to multiple modules to simplify maintenance > ------------------------------------------------------------- > > Key: JBDS-3875 > URL: https://issues.jboss.org/browse/JBDS-3875 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Pavol Pitonak > Labels: havoc > Fix For: 10.0.0.Alpha2 > > > Following up from JBDS-3851. Split the gulpfile into separate modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-279) Component/ infrastructure upgrade for JBTIS 4.1.5/ JBDSIS 7.0.2

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-279?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-279. ----------------------------------- Closed as obsolete > Component/ infrastructure upgrade for JBTIS 4.1.5/ JBDSIS 7.0.2 > --------------------------------------------------------------- > > Key: JBTIS-279 > URL: https://issues.jboss.org/browse/JBTIS-279 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 4.1.4.Final, 7.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > > Update Fuse, Teiid and SwitchYard + poms etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016