May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24441) Import wizard: "Do not clone - use existing repository" still enabled even though no repo exists

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24441: ---------------------------------------- Summary: Import wizard: "Do not clone - use existing repository" still enabled even though no repo exists Key: JBIDE-24441 URL: https://issues.jboss.org/browse/JBIDE-24441 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.4.Final Reporter: Andre Dietisheim Priority: Minor Attachments: image-2017-05-15-11-26-27-131.png, image-2017-05-15-11-31-02-611.png -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23279: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Exception generated when OS 3 connection URL is invalid > ------------------------------------------------------- > > Key: JBIDE-23279 > URL: https://issues.jboss.org/browse/JBIDE-23279 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > > EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application > EXEC: select <New Connection> > EXEC: enter invalid URL in the host field > ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23279: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Exception generated when OS 3 connection URL is invalid > ------------------------------------------------------- > > Key: JBIDE-23279 > URL: https://issues.jboss.org/browse/JBIDE-23279 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > > EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application > EXEC: select <New Connection> > EXEC: enter invalid URL in the host field > ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22075: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22075: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: debug-button-toolbar.png, error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4394) Add requirement rh-java-common-google-gson

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4394: ---------------------------------- Summary: Add requirement rh-java-common-google-gson Key: JBDS-4394 URL: https://issues.jboss.org/browse/JBDS-4394 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: build, rpm Affects Versions: 11.0.0.AM1 Reporter: Lukáš Valach Assignee: Nick Boldt Fix For: 11.0.0.AM1 Add requirement rh-java-common-google-gson to the RPM spec file \[1\]. \[1\] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/devstu... ---- *Reason:* After update form Devstudio 10.2 to 10.4 I had this error in the eclipse log: {code} !ENTRY org.eclipse.jgit.pgm 4 0 2017-05-12 14:03:44.808 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.jgit.pgm [231] Unresolved requirement: Import-Package: org.eclipse.jgit.lfs.server.fs; version="[4.6.1,4.7.0)" -> Export-Package: org.eclipse.jgit.lfs.server.fs; bundle-symbolic-name="org.eclipse.jgit.lfs.server"; bundle-version="4.6.1.201703071140-r"; version="4.6.1"; uses:="javax.servlet, javax.servlet.http, org.eclipse.jgit.lfs.server, org.eclipse.jgit.lfs.lib" org.eclipse.jgit.lfs.server [230] Unresolved requirement: Import-Package: com.google.gson; version="[2.2.4,3.0.0)" Unresolved requirement: Import-Package: org.eclipse.jgit.lfs.server; version="[4.6.1,4.7.0)" -> Export-Package: org.eclipse.jgit.lfs.server; bundle-symbolic-name="org.eclipse.jgit.lfs.server"; bundle-version="4.6.1.201703071140-r"; version="4.6.1"; uses:="javax.servlet.http, org.eclipse.jgit.lfs.lib" ... ... !ENTRY org.eclipse.wst.jsdt.js.node 4 0 2017-05-12 14:03:46.661 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.wst.jsdt.js.node [653] Unresolved requirement: Require-Bundle: com.google.gson; bundle-version="[2.2.4,3.0.0)" {code} Steps to reproduce: # Disable RHSCL 2.4 and Devstudio snapshot repo # Add RHSCL 2.3 and Devstudio stable repo # yum remove rh-* # yum install rh-eclipse46-devstudio (should install 10.2.0.GA) # check if eclipse works (I had no errors in the log) # Disable RHSCL 2.3 and Devstudio stable repo # Enable RHSCL 2.4 and Devstudio snapshot repo # rm -rf ~/.eclipse # Start the Eclipse with -clean # There should be error I mentioned above. I didn't see any impact to users, egit worked fine. # sudo yum update "rh-*" {code} Updating: rh-java-common-google-gson noarch 2.2.4-1.el7 rh-eclipse46-build 177 k rh-java-common-javapackages-tools noarch 4.3.2-1.14.el7 rh-eclipse46-build 95 k rh-java-common-lucene5 noarch 5.4.1-2.3.el7 rh-eclipse46-build 2.2 M rh-java-common-lucene5-analysis noarch 5.4.1-2.3.el7 rh-eclipse46-build 1.3 M rh-java-common-lucene5-analyzers-smartcn noarch 5.4.1-2.3.el7 rh-eclipse46-build 3.4 M rh-java-common-lucene5-queries noarch 5.4.1-2.3.el7 rh-eclipse46-build 211 k rh-java-common-lucene5-queryparser noarch 5.4.1-2.3.el7 rh-eclipse46-build 339 k rh-java-common-lucene5-sandbox noarch 5.4.1-2.3.el7 rh-eclipse46-build 246 k rh-java-common-python-javapackages noarch 4.3.2-1.14.el7 rh-eclipse46-build 87 k rh-maven33-runtime {code} # Restart Eclipse, it will start without errors. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Labels: oc_binary openshift_v3 preferences (was: oc_binary preferences) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.5.0.AM1 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23899) Refactor the OpenShift server adapter to meet new needs (Vert.x, Swarm, ...)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23899?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23899: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Refactor the OpenShift server adapter to meet new needs (Vert.x, Swarm,...) > --------------------------------------------------------------------------- > > Key: JBIDE-23899 > URL: https://issues.jboss.org/browse/JBIDE-23899 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Labels: openshift > Fix For: 4.5.0.AM1 > > > The current version of the OpenShift server adapter has some drawbacks: > - code is linked with EAP/Wildfly on one side and NodeJS on the other > - apart from those two stacks, we don't support others (FUSE, Vert.x,Swarm,...) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-21593. -------------------------------------- Resolution: Cannot Reproduce Bug Can't reproduce even though tried many, many times. Resolving > Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21593 > URL: https://issues.jboss.org/browse/JBIDE-21593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, explorer, openshift_v3 > Fix For: 4.4.4.Final > > Attachments: empty_project.png > > > When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot > !empty_project.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.5.0.AM1 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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