August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-359) Remove Log in Docker Explorer is not working [EBZ#497822]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-359?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-359: --------------------------------- Assignee: Jeff Johnston > Remove Log in Docker Explorer is not working [EBZ#497822] > --------------------------------------------------------- > > Key: ERT-359 > URL: https://issues.jboss.org/browse/ERT-359 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > > Steps to reproduce: > 1. Run in console: docker run -d -p 5000:5000 -v /home/jkopriva/temp2/config1.yml:/etc/docker/registry/config.yml:rw --name registry11 registry:2 > 2. Connect with Docker Tooling to Docker instance. > 3. Click on Display log on registry11 container > 4. Log is displayed in console view. > 5. Remove Log of registry11 container in Docker Explorer. > 6. Run registry11. > 7. Log is not deleted > Docker version: > Docker version 1.10.3, build 19b5791/1.10.3 > Eclipse version: > Eclipse Java EE IDE for Web Developers. > Version: Neon Release (4.6.0) > Build id: 20160613-1800 > Docker Tooling version: > 2.1.0.201607122122 > System: > Fedora 24 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22640: ------------------------------------- Sprint: devex #119 August 2016 (was: devex #118 July 2016) > Server Adapter Editor: Update to Openshift server adapter is not saved > ---------------------------------------------------------------------- > > Key: JBIDE-22640 > URL: https://issues.jboss.org/browse/JBIDE-22640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.1.Final > > > ASSERT: create an Openshift3 connection > ASSERT: create a server adapter from that connection > ASSERT: delete the Openshift3 connection > EXEC: open the server adapter > ASSERT: the connection filed is blank > EXEC: using the dropdown change the connection > ASSERT: the dirty flag of the server editor is not set > EXEC: close the server editor > EXEC: open the server editor again > ASSERT: the connection field is still blank -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22653: ------------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.Final > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22640: ------------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > Server Adapter Editor: Update to Openshift server adapter is not saved > ---------------------------------------------------------------------- > > Key: JBIDE-22640 > URL: https://issues.jboss.org/browse/JBIDE-22640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.1.Final > > > ASSERT: create an Openshift3 connection > ASSERT: create a server adapter from that connection > ASSERT: delete the Openshift3 connection > EXEC: open the server adapter > ASSERT: the connection filed is blank > EXEC: using the dropdown change the connection > ASSERT: the dirty flag of the server editor is not set > EXEC: close the server editor > EXEC: open the server editor again > ASSERT: the connection field is still blank -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Sprint: devex #119 August 2016 (was: devex #118 July 2016) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 3 days > Remaining Estimate: 3 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22653: ------------------------------------- Sprint: devex #119 August 2016 (was: devex #118 July 2016) > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22439: ------------------------------------- Sprint: devex #119 August 2016 (was: devex #118 July 2016) > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.1.Final > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 day, 5 hours, 30 minutes > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22439: ------------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.1.Final > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 day, 5 hours, 30 minutes > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22816: ------------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.1.AM3) > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.1.Final > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22816: ------------------------------------- Sprint: devex #119 August 2016 (was: devex #118 July 2016) > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.1.Final > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 August 2016