[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3562:
-------------------------------------
[~maxandersen], it's not out yet. Looking at the ticket [1] it should be ready on CSP staging when Chris O'Brien gets online this morning (not sure where he is, probably US eastern time). So we could still rebuild using the correct update site, but it would delay it for a day (or two) I assume.
[1] https://engineering.redhat.com/rt/Ticket/Display.html?id=382279
> Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
> --------------------------------------------------------------------------
>
> Key: JBDS-3562
> URL: https://issues.jboss.org/browse/JBDS-3562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.CVE-2015-7501-GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.CVE-2015-7501-GA
>
> Attachments: 900GAvs901GA_B6.p2diff.txt, JBDS900GA-respin_diffs__EAP640-BZ1281963.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png, JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png, JBDS900GA-respin_diffs__p2director.manifest.mf.png, JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png, JBDS900GA-respin_diffs__readme.txt.png
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3562:
-------------------------------------------
https://devstudio.redhat.com/9.0/stable/updates/ is not a site to use for building - it is an enduser updatesite.
So did the new installer go out with different content or did we fix this so we use a build-friendly updatsite ?
> Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)
> --------------------------------------------------------------------------
>
> Key: JBDS-3562
> URL: https://issues.jboss.org/browse/JBDS-3562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.CVE-2015-7501-GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.CVE-2015-7501-GA
>
> Attachments: 900GAvs901GA_B6.p2diff.txt, JBDS900GA-respin_diffs__EAP640-BZ1281963.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png, JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png, JBDS900GA-respin_diffs__p2director.manifest.mf.png, JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png, JBDS900GA-respin_diffs__readme.txt.png
>
>
> Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
> Because JBDS 9.0.0 includes the compromised version of
> apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which
> will include:
> a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
> b) repin of JBDS update sites and installer jars
> To that end, I've created the following new branches:
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
> https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
> And I've bumped the version of the target platforms in the 4.50.x and
> 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
> respectively.
> JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
> 4.3.1.x branch.
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
> (new, 9.0.1)
> https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
> (updated to 9.1.0)
> So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
> 9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21199) AssertionFailedException invoking menu on a server.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21199?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21199:
-------------------------------------
Unfortunately, the wtp servertools event framework doesn't give us any real opportunity to recognize a rename of a runtime. The closest we could come is a runtime changed event, but the event has no details. It only references which runtime was changed, but doesn't say how. I'm not even sure that that's the event that'd be called, though. It might instead call runtimeRemoved() and runtimeAdded().
>From a programatic perspective, there's really no way for me to know that a runtime has just been renamed.
> AssertionFailedException invoking menu on a server.
> ---------------------------------------------------
>
> Key: JBIDE-21199
> URL: https://issues.jboss.org/browse/JBIDE-21199
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> 1. Create a server with a JBoss runtime.
> 2. Make sure that context menu is invoked without exceptions.
> 3. Open Preferences/Server/Runtime Environments and rename the runtime environment bound to the server.
> 4. Invoke contex menu.
> Menu is opened, but there is logged exception:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 2 2015-12-07 14:45:35.604
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.eclipse.core.runtime.Path.initialize(Path.java:641)
> at org.eclipse.core.runtime.Path.<init>(Path.java:238)
> at org.eclipse.core.runtime.Path.<init>(Path.java:186)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.makeRelative(LocalDeploymentOptionsController.java:44)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.getDeployFolder(LocalDeploymentOptionsController.java:68)
> at org.jboss.tools.as.core.server.controllable.systems.AbstractJBossDeploymentOptionsController.getDeploymentsRootFolder(AbstractJBossDeploymentOptionsController.java:78)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getPath(LocalExploreBehavior.java:105)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getDeployDirectory(LocalExploreBehavior.java:62)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExploreServer(LocalExploreBehavior.java:81)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExplore(LocalExploreBehavior.java:34)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.fillContextMenu(ExploreActionProvider.java:102)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:225)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:219)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:174)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:267)
> at org.eclipse.ui.navigator.CommonNavigatorManager$3.menuAboutToShow(CommonNavigatorManager.java:283)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1351)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1332)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:3861)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
> 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:497)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
> I think we should prevent that exception.
> 5. Open the server in editor. Its 'Runtime Environment' is empty, which means that server lost connection to the renamed environment. Can we do something to prevent it, or is it an upstream issue, or is it an expected behavior?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21199) AssertionFailedException invoking menu on a server.
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21199?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21199:
-----------------------------------------------
Renaming of runtime makes servers referencing it incorrect. Can we listen to runtime rename and modify affected servers?
> AssertionFailedException invoking menu on a server.
> ---------------------------------------------------
>
> Key: JBIDE-21199
> URL: https://issues.jboss.org/browse/JBIDE-21199
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> 1. Create a server with a JBoss runtime.
> 2. Make sure that context menu is invoked without exceptions.
> 3. Open Preferences/Server/Runtime Environments and rename the runtime environment bound to the server.
> 4. Invoke contex menu.
> Menu is opened, but there is logged exception:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 2 2015-12-07 14:45:35.604
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.eclipse.core.runtime.Path.initialize(Path.java:641)
> at org.eclipse.core.runtime.Path.<init>(Path.java:238)
> at org.eclipse.core.runtime.Path.<init>(Path.java:186)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.makeRelative(LocalDeploymentOptionsController.java:44)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.getDeployFolder(LocalDeploymentOptionsController.java:68)
> at org.jboss.tools.as.core.server.controllable.systems.AbstractJBossDeploymentOptionsController.getDeploymentsRootFolder(AbstractJBossDeploymentOptionsController.java:78)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getPath(LocalExploreBehavior.java:105)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getDeployDirectory(LocalExploreBehavior.java:62)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExploreServer(LocalExploreBehavior.java:81)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExplore(LocalExploreBehavior.java:34)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.fillContextMenu(ExploreActionProvider.java:102)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:225)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:219)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:174)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:267)
> at org.eclipse.ui.navigator.CommonNavigatorManager$3.menuAboutToShow(CommonNavigatorManager.java:283)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1351)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1332)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:3861)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
> 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:497)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
> I think we should prevent that exception.
> 5. Open the server in editor. Its 'Runtime Environment' is empty, which means that server lost connection to the renamed environment. Can we do something to prevent it, or is it an upstream issue, or is it an expected behavior?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21199) AssertionFailedException invoking menu on a server.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21199?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21199.
---------------------------------
Fix Version/s: 4.3.1.Beta1
Assignee: Rob Stryker
Resolution: Done
pushed to master and maintenance. Fix was simple null check which needed to be passed up a few layers of the stack.
> AssertionFailedException invoking menu on a server.
> ---------------------------------------------------
>
> Key: JBIDE-21199
> URL: https://issues.jboss.org/browse/JBIDE-21199
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> 1. Create a server with a JBoss runtime.
> 2. Make sure that context menu is invoked without exceptions.
> 3. Open Preferences/Server/Runtime Environments and rename the runtime environment bound to the server.
> 4. Invoke contex menu.
> Menu is opened, but there is logged exception:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 2 2015-12-07 14:45:35.604
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.eclipse.core.runtime.Path.initialize(Path.java:641)
> at org.eclipse.core.runtime.Path.<init>(Path.java:238)
> at org.eclipse.core.runtime.Path.<init>(Path.java:186)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.makeRelative(LocalDeploymentOptionsController.java:44)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.getDeployFolder(LocalDeploymentOptionsController.java:68)
> at org.jboss.tools.as.core.server.controllable.systems.AbstractJBossDeploymentOptionsController.getDeploymentsRootFolder(AbstractJBossDeploymentOptionsController.java:78)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getPath(LocalExploreBehavior.java:105)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getDeployDirectory(LocalExploreBehavior.java:62)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExploreServer(LocalExploreBehavior.java:81)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExplore(LocalExploreBehavior.java:34)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.fillContextMenu(ExploreActionProvider.java:102)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:225)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:219)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:174)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:267)
> at org.eclipse.ui.navigator.CommonNavigatorManager$3.menuAboutToShow(CommonNavigatorManager.java:283)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1351)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1332)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:3861)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
> 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:497)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
> I think we should prevent that exception.
> 5. Open the server in editor. Its 'Runtime Environment' is empty, which means that server lost connection to the renamed environment. Can we do something to prevent it, or is it an upstream issue, or is it an expected behavior?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21189) composite install jobs now depends on early access site (thanks to angular JS requirement)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21189?page=com.atlassian.jira.plugi... ]
Denis Golovin reassigned JBIDE-21189:
-------------------------------------
Assignee: Alexey Kazakov (was: Nick Boldt)
> composite install jobs now depends on early access site (thanks to angular JS requirement)
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21189
> URL: https://issues.jboss.org/browse/JBIDE-21189
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, jsp/jsf/xml/html-source-editing, updatesite, upstream
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Recently, jbosstools-jst was updated to depend on a version of angularJS which is only available in our EA site, and therefore installation from the composite site fails unless we add that URL when installing.
> {code}
> [p2.dir] Cannot complete the install because one or more required items could not be found.
> [p2.dir] Software being installed: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> [p2.dir] Missing requirement: Tests Plug-in 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.angularjs.test 3.7.1.Beta1-v20151204-1915-B61) requires 'bundle org.eclipse.angularjs.core 1.1.0' but it could not be found
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: JBoss Tools Java Standard Tools Tests 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> [p2.dir] To: org.jboss.tools.jst.angularjs.test [3.7.1.Beta1-v20151204-1915-B61]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> [p2.dir] To: org.jboss.tools.jst.test.feature.feature.group [3.7.1.Beta1-v20151204-1915-B61]
> [p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-composite-install_4.3.mars/eclipse/configuration/1449257171806.log
> [p2.dir] Installation failed.
> [p2.dir] !SESSION 2015-12-04 14:26:11.552 -----------------------------------------------
> [p2.dir] eclipse.buildId=4.5.1.M20150904-0015
> --
> [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found.
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.880
> [p2.dir] !MESSAGE Software being installed: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881
> [p2.dir] !MESSAGE Missing requirement: Tests Plug-in 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.angularjs.test 3.7.1.Beta1-v20151204-1915-B61) requires 'bundle org.eclipse.angularjs.core 1.1.0' but it could not be found
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2015-12-04 14:27:05.881
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881
> [p2.dir] !MESSAGE From: JBoss Tools Java Standard Tools Tests 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> --
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881
> [p2.dir] !MESSAGE From: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21189) composite install jobs now depends on early access site (thanks to angular JS requirement)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21189?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-21189:
---------------------------------------
linked original issue, introduced this dependency - JBIDE-21001
> composite install jobs now depends on early access site (thanks to angular JS requirement)
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21189
> URL: https://issues.jboss.org/browse/JBIDE-21189
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, jsp/jsf/xml/html-source-editing, updatesite, upstream
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Recently, jbosstools-jst was updated to depend on a version of angularJS which is only available in our EA site, and therefore installation from the composite site fails unless we add that URL when installing.
> {code}
> [p2.dir] Cannot complete the install because one or more required items could not be found.
> [p2.dir] Software being installed: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> [p2.dir] Missing requirement: Tests Plug-in 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.angularjs.test 3.7.1.Beta1-v20151204-1915-B61) requires 'bundle org.eclipse.angularjs.core 1.1.0' but it could not be found
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: JBoss Tools Java Standard Tools Tests 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> [p2.dir] To: org.jboss.tools.jst.angularjs.test [3.7.1.Beta1-v20151204-1915-B61]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> [p2.dir] To: org.jboss.tools.jst.test.feature.feature.group [3.7.1.Beta1-v20151204-1915-B61]
> [p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-composite-install_4.3.mars/eclipse/configuration/1449257171806.log
> [p2.dir] Installation failed.
> [p2.dir] !SESSION 2015-12-04 14:26:11.552 -----------------------------------------------
> [p2.dir] eclipse.buildId=4.5.1.M20150904-0015
> --
> [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found.
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.880
> [p2.dir] !MESSAGE Software being installed: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881
> [p2.dir] !MESSAGE Missing requirement: Tests Plug-in 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.angularjs.test 3.7.1.Beta1-v20151204-1915-B61) requires 'bundle org.eclipse.angularjs.core 1.1.0' but it could not be found
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2015-12-04 14:27:05.881
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881
> [p2.dir] !MESSAGE From: JBoss Tools Java Standard Tools Tests 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> --
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-12-04 14:27:05.881
> [p2.dir] !MESSAGE From: JBoss Tools Java Standard Tools Tests Developer Resources 3.7.1.Beta1-v20151204-1915-B61 (org.jboss.tools.jst.test.feature.source.feature.group 3.7.1.Beta1-v20151204-1915-B61)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21199) AssertionFailedException invoking menu on a server.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21199?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-21199:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.0.Beta1)
> AssertionFailedException invoking menu on a server.
> ---------------------------------------------------
>
> Key: JBIDE-21199
> URL: https://issues.jboss.org/browse/JBIDE-21199
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> 1. Create a server with a JBoss runtime.
> 2. Make sure that context menu is invoked without exceptions.
> 3. Open Preferences/Server/Runtime Environments and rename the runtime environment bound to the server.
> 4. Invoke contex menu.
> Menu is opened, but there is logged exception:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 2 2015-12-07 14:45:35.604
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.eclipse.core.runtime.Path.initialize(Path.java:641)
> at org.eclipse.core.runtime.Path.<init>(Path.java:238)
> at org.eclipse.core.runtime.Path.<init>(Path.java:186)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.makeRelative(LocalDeploymentOptionsController.java:44)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.getDeployFolder(LocalDeploymentOptionsController.java:68)
> at org.jboss.tools.as.core.server.controllable.systems.AbstractJBossDeploymentOptionsController.getDeploymentsRootFolder(AbstractJBossDeploymentOptionsController.java:78)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getPath(LocalExploreBehavior.java:105)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getDeployDirectory(LocalExploreBehavior.java:62)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExploreServer(LocalExploreBehavior.java:81)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExplore(LocalExploreBehavior.java:34)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.fillContextMenu(ExploreActionProvider.java:102)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:225)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:219)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:174)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:267)
> at org.eclipse.ui.navigator.CommonNavigatorManager$3.menuAboutToShow(CommonNavigatorManager.java:283)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1351)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1332)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:3861)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
> 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:497)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
> I think we should prevent that exception.
> 5. Open the server in editor. Its 'Runtime Environment' is empty, which means that server lost connection to the renamed environment. Can we do something to prevent it, or is it an upstream issue, or is it an expected behavior?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21199) AssertionFailedException invoking menu on a server.
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21199?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21199:
--------------------------------
Fix Version/s: 4.3.0.Beta1
> AssertionFailedException invoking menu on a server.
> ---------------------------------------------------
>
> Key: JBIDE-21199
> URL: https://issues.jboss.org/browse/JBIDE-21199
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> 1. Create a server with a JBoss runtime.
> 2. Make sure that context menu is invoked without exceptions.
> 3. Open Preferences/Server/Runtime Environments and rename the runtime environment bound to the server.
> 4. Invoke contex menu.
> Menu is opened, but there is logged exception:
> {code}
> !ENTRY org.eclipse.ui.navigator 4 2 2015-12-07 14:45:35.604
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.eclipse.core.runtime.Path.initialize(Path.java:641)
> at org.eclipse.core.runtime.Path.<init>(Path.java:238)
> at org.eclipse.core.runtime.Path.<init>(Path.java:186)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.makeRelative(LocalDeploymentOptionsController.java:44)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalDeploymentOptionsController.getDeployFolder(LocalDeploymentOptionsController.java:68)
> at org.jboss.tools.as.core.server.controllable.systems.AbstractJBossDeploymentOptionsController.getDeploymentsRootFolder(AbstractJBossDeploymentOptionsController.java:78)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getPath(LocalExploreBehavior.java:105)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.getDeployDirectory(LocalExploreBehavior.java:62)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExploreServer(LocalExploreBehavior.java:81)
> at org.jboss.ide.eclipse.as.ui.subsystems.internal.LocalExploreBehavior.canExplore(LocalExploreBehavior.java:34)
> at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.fillContextMenu(ExploreActionProvider.java:102)
> at org.eclipse.ui.navigator.NavigatorActionService$2.run(NavigatorActionService.java:225)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.navigator.NavigatorActionService.addCommonActionProviderMenu(NavigatorActionService.java:219)
> at org.eclipse.ui.navigator.NavigatorActionService.fillContextMenu(NavigatorActionService.java:174)
> at org.eclipse.ui.navigator.CommonNavigatorManager.fillContextMenu(CommonNavigatorManager.java:267)
> at org.eclipse.ui.navigator.CommonNavigatorManager$3.menuAboutToShow(CommonNavigatorManager.java:283)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1351)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1332)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:3861)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
> 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:497)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
> I think we should prevent that exception.
> 5. Open the server in editor. Its 'Runtime Environment' is empty, which means that server lost connection to the renamed environment. Can we do something to prevent it, or is it an upstream issue, or is it an expected behavior?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months