December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21330) versionwatch should ignore latest symlinks when loading new installers against which to compare

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21330?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21330: ------------------------------- Fix Version/s: 4.3.1.Beta2 > versionwatch should ignore latest symlinks when loading new installers against which to compare > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-21330 > URL: https://issues.jboss.org/browse/JBIDE-21330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: versionwatch > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > Since adding a "latest jar" symlink into the JBDS installer build folders, eg., > https://devstudio.redhat.com/9.0/snapshots/builds/devstudio.product_9.0.m... > we now get a "jbds-9.1.0.latest" installation into ~/static_build_env/jbds/versionwatch/installations. But this folder does not get updated when newer installers are created, so we should ensure that the latest symlinks are NOT used to produce a latest installation folder. > Otherwise we end up with false positive errors like: > {code}Version decreased issues > com.spotify.docker.client 3.1.10.v20151113-2033 > {code}when compared to 3.1.1 in a "seen as newer" (but built earlier so older) latest build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21330) versionwatch should ignore latest symlinks when loading new installers against which to compare

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21330: ---------------------------------- Summary: versionwatch should ignore latest symlinks when loading new installers against which to compare Key: JBIDE-21330 URL: https://issues.jboss.org/browse/JBIDE-21330 Project: Tools (JBoss Tools) Issue Type: Bug Components: versionwatch Affects Versions: 4.3.1.Beta1 Reporter: Nick Boldt Since adding a "latest jar" symlink into the JBDS installer build folders, eg., https://devstudio.redhat.com/9.0/snapshots/builds/devstudio.product_9.0.m... we now get a "jbds-9.1.0.latest" installation into ~/static_build_env/jbds/versionwatch/installations. But this folder does not get updated when newer installers are created, so we should ensure that the latest symlinks are NOT used to produce a latest installation folder. Otherwise we end up with false positive errors like: {code}Version decreased issues com.spotify.docker.client 3.1.10.v20151113-2033 {code}when compared to 3.1.1 in a "seen as newer" (but built earlier so older) latest build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21255) Core/General New and Noteworthy for 4.3.1.Beta1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21255?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-21255. ---------------------------------- Resolution: Rejected Sounds reasonable. Rejecting this one then. > Core/General New and Noteworthy for 4.3.1.Beta1 > ----------------------------------------------- > > Key: JBIDE-21255 > URL: https://issues.jboss.org/browse/JBIDE-21255 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.Beta1 > > > 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 Core/General is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Core/General by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21170) Virtualbox could not be found by CDK adapter

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21170: ----------------------------------- Labels: (was: respin-a) > Virtualbox could not be found by CDK adapter > -------------------------------------------- > > Key: JBIDE-21170 > URL: https://issues.jboss.org/browse/JBIDE-21170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.Beta2 > > > After I set up a CDK server adapter and fixed the wrong path to vagrant in the launch config, I then started the server adapter and got this: > Server CDK Server Adapter at localhost failed to start. > Console: > {code} > The provider 'virtualbox' that was requested to back the machine > 'default' is reporting that it isn't usable on this system. The > reason is shown below: > Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. > Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires > this to be available on the PATH. If VirtualBox is installed, please find the > `VBoxManage` binary and add it to the PATH environmental variable. > {code} > Along with this, there was an Unhandled event loop exception in the error view: > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:520) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > Caused by: java.lang.NullPointerException > at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:359) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:342) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:327) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162) > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 23 more > {code} > In the command line, VBoxManage is accessible and it is located in /usr/local/bin/ and on my PATH. > Max suggested I could try to start Eclipse from command line instead of double-clicking in Finder (which is the normal way to do it on Mac) and that helped. > So for some reason when you start Eclipse using Eclipse.app from Finder, the PATH is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21248) Freemarker New and Noteworthy for 4.3.1.Beta1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21248?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21248: -------------------------------------- Assignee: Alexey Kazakov (was: Denis Golovin) > Freemarker New and Noteworthy for 4.3.1.Beta1 > --------------------------------------------- > > Key: JBIDE-21248 > URL: https://issues.jboss.org/browse/JBIDE-21248 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.1.Beta1 > > > 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 Freemarker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-540) unknown Central categories referenced by JBTIS connectors

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-540?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-540: ----------------------------- Project: JBoss Tools Integration Stack (was: Tools (JBoss Tools)) Key: JBTIS-540 (was: JBIDE-21311) Component/s: distribution (was: central) Affects Version/s: 9.0.0.Alpha2 (was: 4.3.1.Beta1) > unknown Central categories referenced by JBTIS connectors > --------------------------------------------------------- > > Key: JBTIS-540 > URL: https://issues.jboss.org/browse/JBTIS-540 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > > After installing all of JBT 4.3.1.Beta1 from http://download.jboss.org/jbosstools/mars/staging/updates/ into eclipse-jee-mars-1-RC3-linux-gtk-x86_64.tar.gz, then installing all the stuff in Central (including EA content) EXCEPT JRebel and Android connectors, I see this in my console: > {code} > !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.supported' referenced by connector 'org.jboss.runtime.drools.detector.feature' declared in > org.jboss.tools.central.discovery.integration_stack_4.3.0.Alpha2_v20151006_1928_B438.jar_7462569064950840915.jar > !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.bpel.feature' declared in > org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar > !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.drools.eclipse.feature' declared in > org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar > !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.guvnor.tools.feature' declared in > org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-540) unknown Central categories referenced by JBTIS connectors

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-540?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-540: ----------------------------- Affects Version/s: 4.3.0.Alpha2 > unknown Central categories referenced by JBTIS connectors > --------------------------------------------------------- > > Key: JBTIS-540 > URL: https://issues.jboss.org/browse/JBTIS-540 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2, 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > > After installing all of JBT 4.3.1.Beta1 from http://download.jboss.org/jbosstools/mars/staging/updates/ into eclipse-jee-mars-1-RC3-linux-gtk-x86_64.tar.gz, then installing all the stuff in Central (including EA content) EXCEPT JRebel and Android connectors, I see this in my console: > {code} > !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.supported' referenced by connector 'org.jboss.runtime.drools.detector.feature' declared in > org.jboss.tools.central.discovery.integration_stack_4.3.0.Alpha2_v20151006_1928_B438.jar_7462569064950840915.jar > !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.bpel.feature' declared in > org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar > !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.drools.eclipse.feature' declared in > org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar > !MESSAGE Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.guvnor.tools.feature' declared in > org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2_v20151006_1928_B438.jar_6615978320114197060.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21255) Core/General New and Noteworthy for 4.3.1.Beta1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21255?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21255: ------------------------------------- Only CDK server and download-runtimes users this, so I don't think it needs mentioning in server. Foundation+runtimes is enough > Core/General New and Noteworthy for 4.3.1.Beta1 > ----------------------------------------------- > > Key: JBIDE-21255 > URL: https://issues.jboss.org/browse/JBIDE-21255 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.Beta1 > > > 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 Core/General is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Core/General by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21318) OpenShift 2 Server Adapter contains label "... at OpenShift 3"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21318?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21318: ----------------------------------- Fix Version/s: 4.3.1.Beta1 Assignee: Fred Bricon Resolution: Done Labels: respin-a server_adapter (was: server_adapter) > OpenShift 2 Server Adapter contains label "... at OpenShift 3" > --------------------------------------------------------------- > > Key: JBIDE-21318 > URL: https://issues.jboss.org/browse/JBIDE-21318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: server_adapter, respin-a > Fix For: 4.3.1.Beta1 > > > OpenShift 2 server adapters contains in name "... at OpenShift 3". E.g. "applicationName at OpenShift 3". This should be as it was earlier "... at OpenShift" or to distinguish between 2 and 3 we could use "... at OpenShift 2". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21318) OpenShift 2 Server Adapter contains label "... at OpenShift 3"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21318?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21318: ------------------------------------- Fix applied everywhere > OpenShift 2 Server Adapter contains label "... at OpenShift 3" > --------------------------------------------------------------- > > Key: JBIDE-21318 > URL: https://issues.jboss.org/browse/JBIDE-21318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: respin-a, server_adapter > Fix For: 4.3.1.Beta1 > > > OpenShift 2 server adapters contains in name "... at OpenShift 3". E.g. "applicationName at OpenShift 3". This should be as it was earlier "... at OpenShift" or to distinguish between 2 and 3 we could use "... at OpenShift 2". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 December 2015