January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16976) import wizard: Error dialog after importing application without SSH key on PaaS is not enough descriptive

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16976?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16976: ------------------------------------------ setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3. > import wizard: Error dialog after importing application without SSH key on PaaS is not enough descriptive > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16976 > URL: https://issues.jboss.org/browse/JBIDE-16976 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard > Fix For: LATER > > Attachments: error_dialog.png > > > When creating application and following import (git clone after creation process is completed) in case of no SSH key/not added into preferences dialog there is a error dialog with description, that something went wrong during git clone (respectively creating local git repo) and exception thrown. > !error_dialog.png! > It would be nice to have in the dialog, that problem is caused by missing SSH key or at least remove InvocationTargetException from error message - it is useless for user. > Error log stack trace > {code} > java.lang.reflect.InvocationTargetException > at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:176) > at org.jboss.tools.openshift.egit.core.EGitUtils.cloneRepository(EGitUtils.java:270) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.AbstractImportApplicationOperation.cloneRepository(AbstractImportApplicationOperation.java:169) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ImportNewProject.execute(ImportNewProject.java:77) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.importProject(OpenShiftApplicationWizardModel.java:103) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:353) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: java.lang.IllegalStateException: Preference node "null" has been removed. > at org.eclipse.equinox.internal.security.storage.SecurePreferences.checkRemoved(SecurePreferences.java:354) > at org.eclipse.equinox.internal.security.storage.SecurePreferences.nodeExists(SecurePreferences.java:100) > at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.nodeExists(SecurePreferencesWrapper.java:94) > at org.eclipse.egit.core.securestorage.EGitSecureStore.clearCredentials(EGitSecureStore.java:108) > at org.eclipse.egit.ui.internal.credentials.EGitCredentialsProvider.reset(EGitCredentialsProvider.java:142) > at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:125) > at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) > at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:248) > at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) > at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) > at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) > at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1111) > at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:130) > at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:178) > at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:125) > at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:156) > ... 7 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16976) import wizard: Error dialog after importing application without SSH key on PaaS is not enough descriptive

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16976?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16976: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) > import wizard: Error dialog after importing application without SSH key on PaaS is not enough descriptive > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16976 > URL: https://issues.jboss.org/browse/JBIDE-16976 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Labels: application_wizard > Fix For: LATER > > Attachments: error_dialog.png > > > When creating application and following import (git clone after creation process is completed) in case of no SSH key/not added into preferences dialog there is a error dialog with description, that something went wrong during git clone (respectively creating local git repo) and exception thrown. > !error_dialog.png! > It would be nice to have in the dialog, that problem is caused by missing SSH key or at least remove InvocationTargetException from error message - it is useless for user. > Error log stack trace > {code} > java.lang.reflect.InvocationTargetException > at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:176) > at org.jboss.tools.openshift.egit.core.EGitUtils.cloneRepository(EGitUtils.java:270) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.AbstractImportApplicationOperation.cloneRepository(AbstractImportApplicationOperation.java:169) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.importoperation.ImportNewProject.execute(ImportNewProject.java:77) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizardModel.importProject(OpenShiftApplicationWizardModel.java:103) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.OpenShiftApplicationWizard$ImportJob.runInWorkspace(OpenShiftApplicationWizard.java:353) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: java.lang.IllegalStateException: Preference node "null" has been removed. > at org.eclipse.equinox.internal.security.storage.SecurePreferences.checkRemoved(SecurePreferences.java:354) > at org.eclipse.equinox.internal.security.storage.SecurePreferences.nodeExists(SecurePreferences.java:100) > at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.nodeExists(SecurePreferencesWrapper.java:94) > at org.eclipse.egit.core.securestorage.EGitSecureStore.clearCredentials(EGitSecureStore.java:108) > at org.eclipse.egit.ui.internal.credentials.EGitCredentialsProvider.reset(EGitCredentialsProvider.java:142) > at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:125) > at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121) > at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:248) > at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147) > at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) > at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) > at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1111) > at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:130) > at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:178) > at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:125) > at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:156) > ... 7 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19017: ------------------------------------ Central, Forge, WS are now rebuilding: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Prepare for 4.2.2.Final release > ------------------------------- > > Key: JBIDE-19017 > URL: https://issues.jboss.org/browse/JBIDE-19017 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.2.Final > > > TODOs for preparing for the 4.2.2 release. > For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: > a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK > b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13303) errors in error log when navigating openshift explorer and no connection setup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13303?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13303: ------------------------------------- Fix Version/s: 4.3.x > errors in error log when navigating openshift explorer and no connection setup > ------------------------------------------------------------------------------ > > Key: JBIDE-13303 > URL: https://issues.jboss.org/browse/JBIDE-13303 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Max Rydahl Andersen > Priority: Minor > Labels: connection_wizard > Fix For: 4.2.x, 4.3.x > > > Open openshift explorer with properties view and no connection open and no network attached. > com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.UnknownHostException: openshift.redhat.com > at com.openshift.internal.client.RestService.request(RestService.java:103) > at com.openshift.internal.client.RestService.request(RestService.java:91) > at com.openshift.internal.client.RestService.request(RestService.java:72) > at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:135) > at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:104) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:219) > at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:199) > at org.jboss.tools.openshift.express.internal.ui.property.UserPropertySource$1.run(UserPropertySource.java:112) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.net.UnknownHostException: openshift.redhat.com > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:194) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:99) > at com.openshift.internal.client.RestService.request(RestService.java:139) > at com.openshift.internal.client.RestService.request(RestService.java:97) > ... 9 more > Caused by: java.net.UnknownHostException: openshift.redhat.com > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) > at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1491) > at java.security.AccessController.doPrivileged(Native Method) > at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1485) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:177) > ... 12 more > Caused by: java.net.UnknownHostException: openshift.redhat.com > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432) > at java.net.Socket.connect(Socket.java:529) > at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:570) > at sun.net.NetworkClient.doConnect(NetworkClient.java:158) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:523) > at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272) > at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172) > at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911) > at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:94) > ... 11 more -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14630) server adapter wizard: custom deploy folder is not set to adapter that is created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14630?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14630: ------------------------------------- Fix Version/s: LATER (was: 4.2.x) > server adapter wizard: custom deploy folder is not set to adapter that is created > --------------------------------------------------------------------------------- > > Key: JBIDE-14630 > URL: https://issues.jboss.org/browse/JBIDE-14630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Labels: server_adapter_wizard > Fix For: LATER > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14630) server adapter wizard: custom deploy folder is not set to adapter that is created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14630?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14630: ------------------------------------------ setting fixVersion to LATER since the main focus now is to create tooling for OpenShift v3. > server adapter wizard: custom deploy folder is not set to adapter that is created > --------------------------------------------------------------------------------- > > Key: JBIDE-14630 > URL: https://issues.jboss.org/browse/JBIDE-14630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Labels: server_adapter_wizard > Fix For: LATER > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19017: ---------------------------------------- Comment from Nick: "nothing to change in parent pom (no new target platform)". So we don't need a new parent pom. Thanks for the clarification. > Prepare for 4.2.2.Final release > ------------------------------- > > Key: JBIDE-19017 > URL: https://issues.jboss.org/browse/JBIDE-19017 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.2.Final > > > TODOs for preparing for the 4.2.2 release. > For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS: > a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK > b) ensure components have properly upversioned to 4.2.2/8.0.2, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14630) server adapter wizard: custom deploy folder is not set to adapter that is created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14630?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14630: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have at least 1 connection with 1 application # EXEC: from OpenShift Explorer pick *Create Server Adapter* # EXEC: in the upcoming wizard hit *Browse* and set the *deployment folder* to some custom value, hit *Finish* # EXEC: open freshly created server adapter in editor and check what deployment folder is displayed Result: The output folder is not the custom folder you've chosen Expected result: The output folder matches the custom folder you've set in the wizard was: # ASSERT: make sure that you have at least 1 connection with 1 application # EXEC: from OpenShift Explorer pick *Create Server Adapter* # EXEC: in the upcoming wizard hit *Browse* and set the deployment folder to some custom value, hit *Finish* # EXEC: open freshly created server adapter in editor and check what deployment folder is displayed Result: The output folder is not the custom folder you've chosen Expected result: The output folder matches the custom folder you've set in the wizard > server adapter wizard: custom deploy folder is not set to adapter that is created > --------------------------------------------------------------------------------- > > Key: JBIDE-14630 > URL: https://issues.jboss.org/browse/JBIDE-14630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Labels: server_adapter_wizard > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19021) JBoss Central New and Noteworthy for 4.2.2.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19021?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19021: -------------------------------------- Assignee: Fred Bricon > JBoss Central New and Noteworthy for 4.2.2.Final > ------------------------------------------------ > > Key: JBIDE-19021 > URL: https://issues.jboss.org/browse/JBIDE-19021 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.2.2.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If JBoss Central is not listed here check if there are issues that should be added and add them. > Document the ones relevant for JBoss Central by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14630) server adapter wizard: custom deploy folder is not set to adapter that is created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14630?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14630: ------------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-openshift/pull/139) > server adapter wizard: custom deploy folder is not set to adapter that is created > --------------------------------------------------------------------------------- > > Key: JBIDE-14630 > URL: https://issues.jboss.org/browse/JBIDE-14630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Labels: server_adapter_wizard > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 2015