September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18260) cannot open properties pages for a launch because of tern NPE'ing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18260?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18260: --------------------------------------------- video showing the bug: https://v.usetapes.com/E19KVRqEaU > cannot open properties pages for a launch because of tern NPE'ing > ----------------------------------------------------------------- > > Key: JBIDE-18260 > URL: https://issues.jboss.org/browse/JBIDE-18260 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.2.0.CR1 > > > I launch JBoss, then go under Debug to find the process to see the parameters and I get a blank page saying there are invalid values. > In error log is this: > java.lang.NullPointerException > at tern.eclipse.ide.ui.properties.TernModulesPropertyPage.createContents(TernModulesPropertyPage.java:62) > at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233) > at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1537) > at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1289) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178) > at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1281) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:699) > at org.eclipse.jface.preference.PreferenceDialog$9$1.run(PreferenceDialog.java:730) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:725) > at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178) > at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873) > at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1708) > at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1093) > at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1083) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:757) > at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:390) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:385) > at org.eclipse.jface.window.Window.create(Window.java:435) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101) > at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:83) > at org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:177) > at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:519) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18261) When connectors have same ids, priority should be given to early-access

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18261?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18261: --------------------------------------------- what [~fbricon] says. If we actually compared the version of the connector I could see a point, but since a connector can and will have multiple versions and different lists between earlyaccess and normal i cannot see this versioncomparator do much that is not done simpler by just saying EA always win. > When connectors have same ids, priority should be given to early-access > ----------------------------------------------------------------------- > > Key: JBIDE-18261 > URL: https://issues.jboss.org/browse/JBIDE-18261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Labels: respin-a > Fix For: 4.2.0.CR1 > > > Assuming we have 2 discoveyr connectors with same IDs (example of AngularJS vs AngularJS+Ionic), then when both are visible, priority should be given to the one which is early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17621) When you add a runtime to a runtime-less server, you cannot remove it again

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17621?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17621. --------------------------------- Works as described by Rob / as expected. Verified in JBDS 8.0.0.CR1 B201 > When you add a runtime to a runtime-less server, you cannot remove it again > --------------------------------------------------------------------------- > > Key: JBIDE-17621 > URL: https://issues.jboss.org/browse/JBIDE-17621 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > Attachments: JBIDE-17621.png, JBIDE-17621.v2.png > > > When you create a remote server without a runtime and then open the server editor and click the runtime drop down menu, a suitable runtime will be selected. But once you do that, you can no longer revert that action (once you save the editor). > Clearly, there needs to be a new item in the drop down menu called <none> or something similar. > Credit for spotting this bug goes to [~ljelinko] ;) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18263) when I install arquillian in jboss tools i says early access is installed - that is only true for devstudio

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18263?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-18263. --------------------------------------- Fix Version/s: 4.2.0.CR1 Resolution: Rejected rejecting for now. not critical. > when I install arquillian in jboss tools i says early access is installed - that is only true for devstudio > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18263 > URL: https://issues.jboss.org/browse/JBIDE-18263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > arquillian is part of the main site of jboss tools and afaics only in earlyaccess of devstudio. > Looks like the metadata for whats is earlyaccess is wrong or ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18263) when I install arquillian in jboss tools i says early access is installed - that is only true for devstudio

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18263?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18263: --------------------------------------------- weird - arquillian was only marked as earlyaccss in devstudio in past. > when I install arquillian in jboss tools i says early access is installed - that is only true for devstudio > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18263 > URL: https://issues.jboss.org/browse/JBIDE-18263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > arquillian is part of the main site of jboss tools and afaics only in earlyaccess of devstudio. > Looks like the metadata for whats is earlyaccess is wrong or ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14375) Forge should reuse proxy settings from Eclipse

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14375?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-14375. ------------------------------ Verified in JBT 4.2.0.CR1 build. > Forge should reuse proxy settings from Eclipse > ---------------------------------------------- > > Key: JBIDE-14375 > URL: https://issues.jboss.org/browse/JBIDE-14375 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: George Gastaldi > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.2.0.CR1 > > > Forge when running in eclipse should use pre-configured eclipse proxy settings. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14375) Forge should reuse proxy settings from Eclipse

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14375?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-14375: ------------------------------------ I've setup an isolated environment and then in forge I've executed `run http:\\google.com` to prove that proxy settings work. Hovever if there is proxy defined in ~/.forge/config.xml then it overrides eclipse proxy settings. This is currently desired. > Forge should reuse proxy settings from Eclipse > ---------------------------------------------- > > Key: JBIDE-14375 > URL: https://issues.jboss.org/browse/JBIDE-14375 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Alpha2 > Reporter: George Gastaldi > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.2.0.CR1 > > > Forge when running in eclipse should use pre-configured eclipse proxy settings. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17821) Management / Filesystem operations offerred when changing the profile of EAP 5 - CR1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17821?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17821. --------------------------------- Verified in JBDS 8.0.0.CR1 B201 > Management / Filesystem operations offerred when changing the profile of EAP 5 - CR1 > ------------------------------------------------------------------------------------ > > Key: JBIDE-17821 > URL: https://issues.jboss.org/browse/JBIDE-17821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > This is a followup of JBIDE-17636 which added the possibility to change the server profile after creating it. > But for EAP 5.x, the only thing you should be allowed to change is local/remote, not management/filesystem - this is as7/eap6/wf only. > Sorry if you already have a JIRA for this, I couldn't find it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17847) Bad UI workflow when changing the profile of a server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17847?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17847. --------------------------------- This seems to be working properly now. Verified in JBDS 8.0.0.CR1 B201 > Bad UI workflow when changing the profile of a server > ----------------------------------------------------- > > Key: JBIDE-17847 > URL: https://issues.jboss.org/browse/JBIDE-17847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta3 B172 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR1 > > > When I try to change the profile of a server (e.g. WildFly) between file operations and management, I get stuck in the dialog and nothing happens. It turns out that there is a pop up asking me if I want to reload the server editor, but it opens behind this other dialog, so I don't know it's there. > Shouldn't the profile dialog close when you click Finish? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17939) Move JMX Navigator location to bottom left

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17939?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17939. --------------------------------- Verified in JBDS 8.0.0.CR1 B201 > Move JMX Navigator location to bottom left > ------------------------------------------ > > Key: JBIDE-17939 > URL: https://issues.jboss.org/browse/JBIDE-17939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx, server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > I was quite confused by the UI of JMX Navigator and Properties view - when I was connected to more than 1 local processes, I was wondering which one I was viewing in the Properties view. > It turns out that all throughout Eclipse, the Properties view usually shows details for an item that is currently selected in another view. But this can be confusing, because by default, both JMX Navigator and Properties views use the same window/location. So you never see both of them at once. > Rob suggested that the JMX Navigator could have a default location of botton left - below Project Explorer. I like the idea. But right now we don't display anything in that area. So Rob needs to investigate if this will work. > We need it to work for both scenarios: > 1. Server -> Shown in JMX Navigator > 2. Open the JMX Navigator using Window -> Show view -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 2014