July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22773: ------------------------------------- Sprint: devex #117 July 2016 (was: devex #118 July 2016) > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.4.1.AM2 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22773: ------------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM3) > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.4.1.AM2 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- 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.AM3 (was: 4.4.1.AM2) > 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 > 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: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > 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.AM3 > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours > Remaining Estimate: 1 day, 6 hours > > 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-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22613: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.4.1.AM3 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22621) Server adapter wizard: should be able to import projects to my workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22621?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22621: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Server adapter wizard: should be able to import projects to my workspace > ------------------------------------------------------------------------ > > Key: JBIDE-22621 > URL: https://issues.jboss.org/browse/JBIDE-22621 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.1.AM3 > > Attachments: no-workspace-project-exists.png > > > steps to reproduce: > # ASSERT: have empty workspace > # ASSERT: have at least 1 service in OpenShift > # EXEC: in OpenShift explorer: launch server adapter wizard from context menu of your service > Result: > The Eclipse project text field is erroring and nothing to select, since you have no project in your workspace yet. > !no-workspace-project-exists.png! > There's no way for the user to import a project from OpenShift to the workspace in this wizard. One has to close the wizard and head over to the import wizard first and get back. > Expected result: > I should have a link to the right of "Browse.." which allows me to import a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22319) Make OpenshiftServer implement IConnectionFacade

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22319?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22319: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Make OpenshiftServer implement IConnectionFacade > ------------------------------------------------ > > Key: JBIDE-22319 > URL: https://issues.jboss.org/browse/JBIDE-22319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.1.AM3 > > > Add support for having a jmx conection via JBoss remoting to OpenShiftServer. > * need to add jmx client library > * find out the correct url > * configure deployment config with necessary env, ports, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22376: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.1.AM3 > > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22239: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.4.1.AM3 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22241: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.1.AM3 > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- 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 July 2016