August 2017 - jbosstools-issues - Jboss List Archives

[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.5.1.AM2 (was: 4.5.1.AM1) > 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 > Assignee: Andre Dietisheim > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.5.1.AM2 > > > 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 (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24802) Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24802: -------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.x) > Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24802 > URL: https://issues.jboss.org/browse/JBIDE-24802 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.1.AM1 > > Attachments: Spectacle.F10835.png > > > On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive. > !Spectacle.F10835.png! > And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24872) NullPointerException in ResourceUtils.getBuildConfigFor

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24872?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24872: ------------------------------------------ merged PR [#1545| https://github.com/jbosstools/jbosstools-openshift/pull/1545] into master. Resolving. > NullPointerException in ResourceUtils.getBuildConfigFor > ------------------------------------------------------- > > Key: JBIDE-24872 > URL: https://issues.jboss.org/browse/JBIDE-24872 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Automated Error Reporting Bot > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.5.1.AM2 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > java.lang.NullPointerException: null > at org.jboss.tools.openshift.internal.core.util.ResourceUtils.getBuildConfigFor(ResourceUtils.java:663) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage$11.widgetSelected(ServerSettingsWizardPage.java:494) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > Bundles: > | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 | > | org.jboss.tools.openshift.core | 3.3.3.v20170510-1453 | 3.3.3.v20170510-1453 | > | org.jboss.tools.openshift.ui | 3.3.3.v20170510-2204 | 3.3.3.v20170510-2204 | > Operating Systems: > | Linux | 4.11.11.fc26 | 4.11.11.fc26 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/598bb1a2e4b085ca039... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24758) Server editor complains about wrong runtime folder even if fixed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24758?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24758: -------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.x) > Server editor complains about wrong runtime folder even if fixed > ---------------------------------------------------------------- > > Key: JBIDE-24758 > URL: https://issues.jboss.org/browse/JBIDE-24758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.AM1 > > > I had a runtime and server adapter set up for eap 6.4. I deleted the server on the disk. When I opened the server editor, I was shown a red message in the status bar: > The server's runtime folder does not exist: ...... > So far so good. > So I unzip eap 6.4 somewhere else, clicked Runtime Environment in the server editor, and pointed the runtime to the new correct directory. Then I saved the editor. But the error message in the status bar still won't go away. I have to close the editor and then open it again, then the message no longer shows up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24758) Server editor complains about wrong runtime folder even if fixed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24758?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-24758. --------------------------------- Resolution: Done I think I fixed this... at lesat hte main issue. I cannot replicate the second issue about server not starting :( If that one persists, please open a new issue :( If I didn't fix the editor status, re-open this one. > Server editor complains about wrong runtime folder even if fixed > ---------------------------------------------------------------- > > Key: JBIDE-24758 > URL: https://issues.jboss.org/browse/JBIDE-24758 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.AM1 > > > I had a runtime and server adapter set up for eap 6.4. I deleted the server on the disk. When I opened the server editor, I was shown a red message in the status bar: > The server's runtime folder does not exist: ...... > So far so good. > So I unzip eap 6.4 somewhere else, clicked Runtime Environment in the server editor, and pointed the runtime to the new correct directory. Then I saved the editor. But the error message in the status bar still won't go away. I have to close the editor and then open it again, then the message no longer shows up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24869) Server adapter: add tests for debugging, docker image metadata retrieval etc.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24869?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24869: ------------------------------------------ merged into master > Server adapter: add tests for debugging, docker image metadata retrieval etc. > ----------------------------------------------------------------------------- > > Key: JBIDE-24869 > URL: https://issues.jboss.org/browse/JBIDE-24869 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.1.AM2 > > > In JBIDE-24184 server adapters were refactored and reading docker image metadata to enable/disable devmode and debugging was added. Tests should now get adapted and added to assert the current implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24875) Name of cdk 3 adapter is different depending on using detection or adding manually

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24875?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-24875: --------------------------------------- I believe that current name of CDK 3 server adapter was "Container Development Environment" and runtime detection created "Container Development Environment 3" which is inconsistent. I thought that we wanted to go with "Container Development Environment" name for both CDK (2.x and 3) adapters and that runtime detection will do the same, but it seems that we are having two different names for adapters, "Container Development Environment 3" for CDK 3 and "Container Development Environment" for CDK 2.x adapters. [~rob.stryker] Could you please clarify this? In case that we go with two different names, I just need to know, cause I have to update integration tests. Thanks! > Name of cdk 3 adapter is different depending on using detection or adding manually > ---------------------------------------------------------------------------------- > > Key: JBIDE-24875 > URL: https://issues.jboss.org/browse/JBIDE-24875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.AM1 > > > This is a followup of JBIDE-24447. > When cdk 3 is auto detected (typically when you start devstudio and ~/.minishift exists), the adapter will be created automatically with the name "Container Development Environment 3". On the other hand, if you choose to create the cdk 3 server adapter manually, the default name is "Container Development Environment". These should be consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24875) Name of cdk 3 adapter is different depending on using detection or adding manually

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24875?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-24875: ------------------------------------- Assignee: Rob Stryker (was: Ondrej Dockal) > Name of cdk 3 adapter is different depending on using detection or adding manually > ---------------------------------------------------------------------------------- > > Key: JBIDE-24875 > URL: https://issues.jboss.org/browse/JBIDE-24875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.AM1 > > > This is a followup of JBIDE-24447. > When cdk 3 is auto detected (typically when you start devstudio and ~/.minishift exists), the adapter will be created automatically with the name "Container Development Environment 3". On the other hand, if you choose to create the cdk 3 server adapter manually, the default name is "Container Development Environment". These should be consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24875) Name of cdk 3 adapter is different depending on using detection or adding manually

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24875?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-24875: ------------------------------------- Assignee: Ondrej Dockal (was: Rob Stryker) > Name of cdk 3 adapter is different depending on using detection or adding manually > ---------------------------------------------------------------------------------- > > Key: JBIDE-24875 > URL: https://issues.jboss.org/browse/JBIDE-24875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Ondrej Dockal > Fix For: 4.5.1.AM1 > > > This is a followup of JBIDE-24447. > When cdk 3 is auto detected (typically when you start devstudio and ~/.minishift exists), the adapter will be created automatically with the name "Container Development Environment 3". On the other hand, if you choose to create the cdk 3 server adapter manually, the default name is "Container Development Environment". These should be consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24877: --------------------------------------- OK, I changed it to minor. But it's still pretty odd, so I think it's worth investigating what's going on here. > CDK 2 detection results in CDK 3 adapter creation > ------------------------------------------------- > > Key: JBIDE-24877 > URL: https://issues.jboss.org/browse/JBIDE-24877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > > As described by [~odockal] in JBIDE-24447: > When you start devstudio and it finds cdk 2 installed inside ../../../cdk/ relative to eclipse's config, it will create a cdk 3 server instead of cdk 2. > This relative path normally translate to a structure like this: > $SOME_DIR/devstudio > $SOME_DIR/cdk/YOUR/CDK/2/SOMEWHERE/INSIDE/HERE > BUT... this will only happen in a special situation where you have CDK 2 installed where devstudio looks for it (see above) AND you set up the MINISHIFT_HOME env var to point to your CDK 3 home when you start devstudio. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 2017