September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24236) Preferences: "automagically" use the oc that's shipped with the cdk3

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-24236 at 9/19/17 11:56 AM: ----------------------------------------------------------------- Thanks! It seems to be working. Verified in Version: 11.1.0.AM2 Build id: AM2-v20170914-1647-B1060. Closing. was (Author: odockal): It seems to be working. Verified in Version: 11.1.0.AM2 Build id: AM2-v20170914-1647-B1060. Closing. > Preferences: "automagically" use the oc that's shipped with the cdk3 > -------------------------------------------------------------------- > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.Final > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24236) Preferences: "automagically" use the oc that's shipped with the cdk3

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-24236. --------------------------------- > Preferences: "automagically" use the oc that's shipped with the cdk3 > -------------------------------------------------------------------- > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.Final > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24236) Preferences: "automagically" use the oc that's shipped with the cdk3

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-24236: --------------------------------------- It seems to be working. Verified in Version: 11.1.0.AM2 Build id: AM2-v20170914-1647-B1060. Closing. > Preferences: "automagically" use the oc that's shipped with the cdk3 > -------------------------------------------------------------------- > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.Final > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4541) update SpringIDE to 3.9 in Central?

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4541?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4541: ---------------------------------- What's the rationale for installing SpringIDE in DevStudio ? Spring specific dev tools ? > update SpringIDE to 3.9 in Central? > ----------------------------------- > > Key: JBDS-4541 > URL: https://issues.jboss.org/browse/JBDS-4541 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > > org.springframework.ide.eclipse.feature.feature.group 3.9.0.201707061730-RELEASE is available from http://dist.springsource.com/release/TOOLS/update/e4.7 > Do we want to update to the latest? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4540) Remove findbugs plugin from Central

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4540?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-4540: ------------------------------------- ok, thanks, that's fine with me. > Remove findbugs plugin from Central > ----------------------------------- > > Key: JBDS-4540 > URL: https://issues.jboss.org/browse/JBDS-4540 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: central-update > Affects Versions: 11.1.0.AM1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > I suggest we remove FindBugs connector from Central. It seems it hasn't been developed for some time now. The version we have in central is: > edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1 > And if you look at the project's update site, that's still the latest release there is: > http://findbugs.cs.umd.edu/eclipse/ > Furthermore, it kind of broke for me now. I never tested it extensively. But I would create a project and then right-click -> Find Bugs -> Find Bugs. This would open a window showing progress as the project is searched for bugs. When I tried it now, no window appears. For a few seconds something shows up in the status bar. But I can't see the results anywhere. > Since this is Central, we could do this right away - affecting devstudio 11 / jbosstools 4.5.0. But I guess we need PM approval first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4540) Remove findbugs plugin from Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4540?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4540: ---------------------------------- +1 > Remove findbugs plugin from Central > ----------------------------------- > > Key: JBDS-4540 > URL: https://issues.jboss.org/browse/JBDS-4540 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: central-update > Affects Versions: 11.1.0.AM1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > I suggest we remove FindBugs connector from Central. It seems it hasn't been developed for some time now. The version we have in central is: > edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1 > And if you look at the project's update site, that's still the latest release there is: > http://findbugs.cs.umd.edu/eclipse/ > Furthermore, it kind of broke for me now. I never tested it extensively. But I would create a project and then right-click -> Find Bugs -> Find Bugs. This would open a window showing progress as the project is searched for bugs. When I tried it now, no window appears. For a few seconds something shows up in the status bar. But I can't see the results anywhere. > Since this is Central, we could do this right away - affecting devstudio 11 / jbosstools 4.5.0. But I guess we need PM approval first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25000: ------------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.1.AM3 > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in OpenShift based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.png! > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Labels: releasework (was: ) > Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.5.1.AM2 > > > * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > * For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) > * And this it wrong too: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't use the /development/ URLs for stable releases) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4540) Remove findbugs plugin from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4540?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4540: ----------------------------- Fix Version/s: 11.1.0.AM3 (was: 11.1.0.AM2) > Remove findbugs plugin from Central > ----------------------------------- > > Key: JBDS-4540 > URL: https://issues.jboss.org/browse/JBDS-4540 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: central-update > Affects Versions: 11.1.0.AM1 > Reporter: Martin Malina > Assignee: Jeff MAURY > Fix For: 11.1.0.AM3 > > > I suggest we remove FindBugs connector from Central. It seems it hasn't been developed for some time now. The version we have in central is: > edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1 > And if you look at the project's update site, that's still the latest release there is: > http://findbugs.cs.umd.edu/eclipse/ > Furthermore, it kind of broke for me now. I never tested it extensively. But I would create a project and then right-click -> Find Bugs -> Find Bugs. This would open a window showing progress as the project is searched for bugs. When I tried it now, no window appears. For a few seconds something shows up in the status bar. But I can't see the results anywhere. > Since this is Central, we could do this right away - affecting devstudio 11 / jbosstools 4.5.0. But I guess we need PM approval first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4540) Remove findbugs plugin from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4540?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4540: -------------------------------- Assignee: Nick Boldt (was: Jeff MAURY) > Remove findbugs plugin from Central > ----------------------------------- > > Key: JBDS-4540 > URL: https://issues.jboss.org/browse/JBDS-4540 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: central-update > Affects Versions: 11.1.0.AM1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > > I suggest we remove FindBugs connector from Central. It seems it hasn't been developed for some time now. The version we have in central is: > edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1 > And if you look at the project's update site, that's still the latest release there is: > http://findbugs.cs.umd.edu/eclipse/ > Furthermore, it kind of broke for me now. I never tested it extensively. But I would create a project and then right-click -> Find Bugs -> Find Bugs. This would open a window showing progress as the project is searched for bugs. When I tried it now, no window appears. For a few seconds something shows up in the status bar. But I can't see the results anywhere. > Since this is Central, we could do this right away - affecting devstudio 11 / jbosstools 4.5.0. But I guess we need PM approval first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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