December 2015 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-695) Review: 9.1.0 Beta1 Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-695?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-695: ---------------------------------------- AT the end, you have this: {quote} In all cases, for more information see Install Red Hat JBoss Developer Studio and Update Red Hat JBoss Developer Studio. {quote} It contains links to the two docs. But the links have 9.0 in the url. So I'm afraid it will not point to 9.1.0.Beta1 docs correctly. That's all. > Review: 9.1.0 Beta1 Release Notes > --------------------------------- > > Key: TOOLSDOC-695 > URL: https://issues.jboss.org/browse/TOOLSDOC-695 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Reporter: Supriya Bharadwaj > Assignee: Martin Malina > > Please review the RNs located at: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-695) Review: 9.1.0 Beta1 Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-695?page=com.atlassian.jira.plug... ] Martin Malina reassigned TOOLSDOC-695: -------------------------------------- Assignee: Supriya Bharadwaj (was: Martin Malina) > Review: 9.1.0 Beta1 Release Notes > --------------------------------- > > Key: TOOLSDOC-695 > URL: https://issues.jboss.org/browse/TOOLSDOC-695 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > > Please review the RNs located at: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-695) Review: 9.1.0 Beta1 Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-695?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-695: ---------------------------------------- The resolved JIRAs filter is wrong, your filter contains resolved JIRAs for all of 9.0.x - more than 500 JIRAs. You want just 9.1 JIRAs, so use this filter instead: {code} (project in (JBDS) AND affectedVersion < 9.1.0.Beta1 AND fixVersion in (9.1.0.Beta1) OR project in (JBIDE) AND affectedVersion < 4.3.1.Beta1 AND fixVersion in (4.3.1.Beta1)) AND type in (Bug) AND resolution in (Done) {code} When we get to Beta2, you will just add Beta2 to the list in fixVersion. The Known Issues filter seems correct. > Review: 9.1.0 Beta1 Release Notes > --------------------------------- > > Key: TOOLSDOC-695 > URL: https://issues.jboss.org/browse/TOOLSDOC-695 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Reporter: Supriya Bharadwaj > Assignee: Martin Malina > > Please review the RNs located at: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-695) Review: 9.1.0 Beta1 Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-695?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-695: ---------------------------------------- ⁠3. New Features Credentialing Framework - you're mixing two articles into one here. The first two paragraphs belong to Improvements on the Importer wizard - see http://tools-stg.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Beta1.... . > Review: 9.1.0 Beta1 Release Notes > --------------------------------- > > Key: TOOLSDOC-695 > URL: https://issues.jboss.org/browse/TOOLSDOC-695 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Reporter: Supriya Bharadwaj > Assignee: Martin Malina > > Please review the RNs located at: http://docbuilder.usersys.redhat.com/23115/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21239) Forge New and Noteworthy for 4.3.1.Beta1

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21239?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21239. ------------------------------ Verified. > Forge New and Noteworthy for 4.3.1.Beta1 > ---------------------------------------- > > Key: JBIDE-21239 > URL: https://issues.jboss.org/browse/JBIDE-21239 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > 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 Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge 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-21249) javascript New and Noteworthy for 4.3.1.Beta1

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21249?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21249. ------------------------------ Verified > javascript New and Noteworthy for 4.3.1.Beta1 > --------------------------------------------- > > Key: JBIDE-21249 > URL: https://issues.jboss.org/browse/JBIDE-21249 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, nodejs > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > 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 javascript is not listed here check if there are issues that should be added and add them. > Document the ones relevant for javascript 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21170: --------------------------------------- [~rob.stryker], see my comment in JBIDE-19974: {quote} The detection still doesn't work for me, but I came up with a command that should work: $SHELL -l -c "env | grep DOCKER" {quote} And then from the upstream BZ https://bugs.eclipse.org/bugs/show_bug.cgi?id=469624 : {quote} Max, actually the current patch will do both -l and -i (AFAIK), because without -i it would not work (according to Xavier). {quote} But to be sure, please check the commit from the BZ. > 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-21170) Virtualbox could not be found by CDK adapter

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21170: --------------------------------------- [~rob.stryker], but it did fix one thing, didn't it? It fixed the call to vagrant status - without this patch, vagrant status didn't work even with the workaround of adding the PATH in the launch config. If you do it like Xavier does it in Docker tools, then you should really get the full path from this call and not just inherited env from Eclipse. > 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-20387) Use column number when navigating to errors, and more

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-20387: --------------------------------------- Fixed here: https://github.com/jbosstools/jbosstools-freemarker/pull/57 > Use column number when navigating to errors, and more > ----------------------------------------------------- > > Key: JBIDE-20387 > URL: https://issues.jboss.org/browse/JBIDE-20387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.3.0.Beta2 > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.x > > > The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): > * {{getColumnNumber()}}, {{getEndColumnNumber()}} > * {{getEndLineNumber()}} > * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21373) Eclipse files are missing from .gitignore

by Daniel Dekany (JIRA)

Daniel Dekany created JBIDE-21373: ------------------------------------- Summary: Eclipse files are missing from .gitignore Key: JBIDE-21373 URL: https://issues.jboss.org/browse/JBIDE-21373 Project: Tools (JBoss Tools) Issue Type: Bug Components: freemarker Reporter: Daniel Dekany Priority: Trivial The Eclipse generated files aren't git ignored, making staging, resets, etc. more difficult. -- 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