January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21457) Explorer: Show build pod in explorer deployment view if it any state other then complete

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21457: ---------------------------------- Summary: Explorer: Show build pod in explorer deployment view if it any state other then complete (was: Explorer: Build changes no longer update tab property view) > Explorer: Show build pod in explorer deployment view if it any state other then complete > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21457 > URL: https://issues.jboss.org/browse/JBIDE-21457 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Labels: openshift_deployment_view > > Starting a build on the server should cause updates to appear in the build tabs. This was broken as part of making pods update correctly in the explorer view tree. Suspect it has something to do with how we find deployments for build pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21457) Explorer: Show build pod in explorer deployment view if it any state other then complete

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21457: ---------------------------------- Issue Type: Enhancement (was: Bug) > Explorer: Show build pod in explorer deployment view if it any state other then complete > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21457 > URL: https://issues.jboss.org/browse/JBIDE-21457 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Labels: openshift_deployment_view > > Starting a build on the server should cause updates to appear in the build tabs. This was broken as part of making pods update correctly in the explorer view tree. Suspect it has something to do with how we find deployments for build pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21458) Explorer: New deployments and pods dont refresh properly in explorer tree

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21458?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21458: ---------------------------------- Fix Version/s: 4.3.1.Beta2 > Explorer: New deployments and pods dont refresh properly in explorer tree > ------------------------------------------------------------------------- > > Key: JBIDE-21458 > URL: https://issues.jboss.org/browse/JBIDE-21458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.Beta2 > > Attachments: Service_added_but_shows_empty_space.png > > > Expanding the explorer tree of a project to see the deployments and pods and then adding a new deployment from the server causes the display to show the wrong nodes and not receive any updates. See screen shot attached: > Demonstrated by: > # From eclipse, add a new project > # Expand project . note: no deployments > # From cli, add a service > # Note screen 'updates' but there is no deployment, just an empty node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21458) Explorer: New deployments and pods dont refresh properly in explorer tree

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21458?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21458: --------------------------------------- Added hack to fix. [~fbricon] please review > Explorer: New deployments and pods dont refresh properly in explorer tree > ------------------------------------------------------------------------- > > Key: JBIDE-21458 > URL: https://issues.jboss.org/browse/JBIDE-21458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.Beta2 > > Attachments: Service_added_but_shows_empty_space.png > > > Expanding the explorer tree of a project to see the deployments and pods and then adding a new deployment from the server causes the display to show the wrong nodes and not receive any updates. See screen shot attached: > Demonstrated by: > # From eclipse, add a new project > # Expand project . note: no deployments > # From cli, add a service > # Note screen 'updates' but there is no deployment, just an empty node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21458) Explorer: New deployments and pods dont refresh properly in explorer tree

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21458?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21458: --------------------------------------- This bug has nothing to do with new project and where they are created but for projects that have nod children. Traced down to http://git.eclipse.org/c/platform/eclipse.platform.ui.git/tree/bundles/or... but am unable to determine why the first child will not be added. [~snjeza] Can you comment or have idea if this is a problem with the wigit or how its being called? > Explorer: New deployments and pods dont refresh properly in explorer tree > ------------------------------------------------------------------------- > > Key: JBIDE-21458 > URL: https://issues.jboss.org/browse/JBIDE-21458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Attachments: Service_added_but_shows_empty_space.png > > > Expanding the explorer tree of a project to see the deployments and pods and then adding a new deployment from the server causes the display to show the wrong nodes and not receive any updates. See screen shot attached: > Demonstrated by: > # From eclipse, add a new project > # Expand project . note: no deployments > # From cli, add a service > # Note screen 'updates' but there is no deployment, just an empty node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21461) Upgrade Forge Runtime to 3.0.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21461?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21461: ---------------------------------------- The PR has been merged into both master and 4.3.x. Resolving. > Upgrade Forge Runtime to 3.0.0.Beta2 > ------------------------------------ > > Key: JBIDE-21461 > URL: https://issues.jboss.org/browse/JBIDE-21461 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.1.Beta1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21461) Upgrade Forge Runtime to 3.0.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21461?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21461: ----------------------------------- Labels: new_and_noteworthy (was: ) > Upgrade Forge Runtime to 3.0.0.Beta2 > ------------------------------------ > > Key: JBIDE-21461 > URL: https://issues.jboss.org/browse/JBIDE-21461 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.1.Beta1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21371?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21371: ----------------------------------------------- Listener checks that there is a waiting instance of MagicProjectChangeJob for the server, and then new job instance is not created. What if there is a running instance of MagicProjectChangeJob? Eclipse may set new instance(s) to different workers and they will run concurrently. > Server Adapter: implement automatic publishing > ---------------------------------------------- > > Key: JBIDE-21371 > URL: https://issues.jboss.org/browse/JBIDE-21371 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > > Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20719) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20719?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20719: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > Updating a token for OpenShift 3 connection via Edit Connection does not update resources > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20719 > URL: https://issues.jboss.org/browse/JBIDE-20719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.1.CR1 > > > If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21139) OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21139?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21139: -------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.3.1.Beta2) > OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing > ------------------------------------------------------------------------------- > > Key: JBIDE-21139 > URL: https://issues.jboss.org/browse/JBIDE-21139 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: connection_wizard, explorer, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: connection.png > > > After editing a connection which was without credentials (e.g. token was not stored in secure storage and eclipse got restarted) and there is tree item informing about such an error, editing the connection does not refresh connection item in OpenShift explorer view and it is necessary to refresh it via context menu of the connection. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016