[JBoss JIRA] (JBIDE-14356) GC overhead limit exceeded when adding fileset to LiveReload Server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14356?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14356:
-------------------------------------
Every time you type in the UI, it is fetchng what paths match that pattern. In this case, it is making an array of all 'matching' paths, which includes every file on your filesystem. Thus, it fails.
It does not do this via a job, and it does not do this with a progress monitor, so ti cannot be canceled. The preview is automatically refreshed. This is an API deficiency.
> GC overhead limit exceeded when adding fileset to LiveReload Server
> -------------------------------------------------------------------
>
> Key: JBIDE-14356
> URL: https://issues.jboss.org/browse/JBIDE-14356
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Reporter: Stian Thorgersen
> Assignee: Rob Stryker
>
> When creating a LiveReload Server and adding a fileset Eclipse hangs consuming a lot of CPU. Eventually the error message "Unhandled event loop exception / GC overhead limit exceeded" is displayed.
> From the stack trace while this is going the only interesting thread is:
> {code}
> "main" prio=10 tid=0x00007ff9a0009800 nid=0x22c2 runnable [0x00007ff9a81fe000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8654)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1243)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2283)
> at org.eclipse.swt.widgets.Shell.setVisible(Shell.java:2153)
> at org.eclipse.swt.widgets.Shell.open(Shell.java:1546)
> at org.eclipse.jface.window.Window.open(Window.java:798)
> at org.eclipse.ui.internal.statushandlers.InternalDialog.open(InternalDialog.java:327)
> at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.doAddStatusAdapter(WorkbenchStatusDialogManagerImpl.java:270)
> at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.addStatusAdapter(WorkbenchStatusDialogManagerImpl.java:197)
> at org.eclipse.ui.statushandlers.WorkbenchStatusDialogManager.addStatusAdapter(WorkbenchStatusDialogManager.java:156)
> at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.showStatusAdapter(WorkbenchErrorHandler.java:101)
> at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:57)
> at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:106)
> at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:242)
> at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopException(WorkbenchAdvisor.java:326)
> at org.eclipse.ui.internal.ExceptionHandler.handleException(ExceptionHandler.java:65)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:830)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.jboss.ide.eclipse.archives.webtools.filesets.FilesetActionProvider$1.run(FilesetActionProvider.java:202)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> I'm running:
> * Eclipse Kepler M6 with JBoss Tools 4.1 Alpha 2
> * OpenJDK 1.7.0_21
> * Ubuntu 13.04
> To reproduce create a new LiveReload server. Expand it, right click on 'Filesets' and select 'Create New File Filter'. Then write '/' in 'Root Directory'. Observe that Eclipse now consumes ~100% cpu on all available cores. Wait for a few minutes and the error message mentioned earlier should be displayed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBIDE-14356) GC overhead limit exceeded when adding fileset to LiveReload Server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14356?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14356:
-------------------------------------
looking into it
> GC overhead limit exceeded when adding fileset to LiveReload Server
> -------------------------------------------------------------------
>
> Key: JBIDE-14356
> URL: https://issues.jboss.org/browse/JBIDE-14356
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Reporter: Stian Thorgersen
> Assignee: Rob Stryker
>
> When creating a LiveReload Server and adding a fileset Eclipse hangs consuming a lot of CPU. Eventually the error message "Unhandled event loop exception / GC overhead limit exceeded" is displayed.
> From the stack trace while this is going the only interesting thread is:
> {code}
> "main" prio=10 tid=0x00007ff9a0009800 nid=0x22c2 runnable [0x00007ff9a81fe000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8654)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1243)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2283)
> at org.eclipse.swt.widgets.Shell.setVisible(Shell.java:2153)
> at org.eclipse.swt.widgets.Shell.open(Shell.java:1546)
> at org.eclipse.jface.window.Window.open(Window.java:798)
> at org.eclipse.ui.internal.statushandlers.InternalDialog.open(InternalDialog.java:327)
> at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.doAddStatusAdapter(WorkbenchStatusDialogManagerImpl.java:270)
> at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.addStatusAdapter(WorkbenchStatusDialogManagerImpl.java:197)
> at org.eclipse.ui.statushandlers.WorkbenchStatusDialogManager.addStatusAdapter(WorkbenchStatusDialogManager.java:156)
> at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.showStatusAdapter(WorkbenchErrorHandler.java:101)
> at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:57)
> at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:106)
> at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:242)
> at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopException(WorkbenchAdvisor.java:326)
> at org.eclipse.ui.internal.ExceptionHandler.handleException(ExceptionHandler.java:65)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:830)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.jboss.ide.eclipse.archives.webtools.filesets.FilesetActionProvider$1.run(FilesetActionProvider.java:202)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> I'm running:
> * Eclipse Kepler M6 with JBoss Tools 4.1 Alpha 2
> * OpenJDK 1.7.0_21
> * Ubuntu 13.04
> To reproduce create a new LiveReload server. Expand it, right click on 'Filesets' and select 'Create New File Filter'. Then write '/' in 'Root Directory'. Observe that Eclipse now consumes ~100% cpu on all available cores. Wait for a few minutes and the error message mentioned earlier should be displayed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBDS-2630) include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-2630?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on JBDS-2630:
-----------------------------------
What files are we looking at?
As far as I know, we have no requirements on websphere, jonas, or generic.jboss, and we do not really want or care if they are installed at all. We do have some tests that run against tomcat, and it's useful to have tomcat in jbds.
So again, what files are we looking at for what needs to change?
> include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2630
> URL: https://issues.jboss.org/browse/JBDS-2630
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: P2 Enabled Product
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
> It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
> So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
> [0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
> --
> Currently, JBDS product feature includes these server adapter plugins & features:
> {code}
> <import plugin="org.eclipse.jst.server.tomcat.core"/>
> <import plugin="org.eclipse.jst.server.tomcat.ui"/>
> <import plugin="org.eclipse.jst.server.websphere.core"/>
> <import plugin="org.eclipse.jst.server.generic.jonas"/>
> <import feature="org.eclipse.jst.server_ui.feature"/>
> <import feature="org.eclipse.jst.server_adapters.feature"/>
> {code}
> And the M7 version of the server_adapters.ext.feature includes these:
> {code}
> <plugin id="org.eclipse.jst.server.tomcat.core"/>
> <plugin id="org.eclipse.jst.server.tomcat.ui"/>
> <plugin id="org.eclipse.jst.server.websphere.core"/> *[removed]*
> <plugin id="org.eclipse.jst.server.generic.jboss"/>
> <plugin id="org.eclipse.jst.server.generic.jonas"/>
> {code}
> So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
> Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
> {code}
> <plugin id="org.eclipse.jst.server.core"/>
> <plugin id="org.eclipse.jst.server.generic.core"/>
> {code}
> [~rob.stryker] WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBDS-2630) include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2630?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2630:
-----------------------------
Description:
Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
[0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
--
Currently, JBDS product feature includes these server adapter plugins & features:
{code}
<import plugin="org.eclipse.jst.server.tomcat.core"/>
<import plugin="org.eclipse.jst.server.tomcat.ui"/>
<import plugin="org.eclipse.jst.server.websphere.core"/> *[removed after M6]*
<import plugin="org.eclipse.jst.server.generic.jonas"/>
<import feature="org.eclipse.jst.server_ui.feature"/>
<import feature="org.eclipse.jst.server_adapters.feature"/>
{code}
And the M7 version of the server_adapters.ext.feature includes these:
{code}
<plugin id="org.eclipse.jst.server.tomcat.core"/>
<plugin id="org.eclipse.jst.server.tomcat.ui"/>
<plugin id="org.eclipse.jst.server.websphere.core"/>
<plugin id="org.eclipse.jst.server.generic.jboss"/>
<plugin id="org.eclipse.jst.server.generic.jonas"/>
{code}
So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
{code}
<plugin id="org.eclipse.jst.server.core"/>
<plugin id="org.eclipse.jst.server.generic.core"/>
{code}
[~rob.stryker] WDYT?
was:
Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
[0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
--
Currently, JBDS product feature includes these server adapter plugins & features:
{code}
<import plugin="org.eclipse.jst.server.tomcat.core"/>
<import plugin="org.eclipse.jst.server.tomcat.ui"/>
<import plugin="org.eclipse.jst.server.websphere.core"/>
<import plugin="org.eclipse.jst.server.generic.jonas"/>
<import feature="org.eclipse.jst.server_ui.feature"/>
<import feature="org.eclipse.jst.server_adapters.feature"/>
{code}
And the M7 version of the server_adapters.ext.feature includes these:
{code}
<plugin id="org.eclipse.jst.server.tomcat.core"/>
<plugin id="org.eclipse.jst.server.tomcat.ui"/>
<plugin id="org.eclipse.jst.server.websphere.core"/>
<plugin id="org.eclipse.jst.server.generic.jboss"/>
<plugin id="org.eclipse.jst.server.generic.jonas"/>
{code}
So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
{code}
<plugin id="org.eclipse.jst.server.core"/>
<plugin id="org.eclipse.jst.server.generic.core"/>
{code}
[~rob.stryker] WDYT?
> include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2630
> URL: https://issues.jboss.org/browse/JBDS-2630
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: P2 Enabled Product
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
> It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
> So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
> [0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
> --
> Currently, JBDS product feature includes these server adapter plugins & features:
> {code}
> <import plugin="org.eclipse.jst.server.tomcat.core"/>
> <import plugin="org.eclipse.jst.server.tomcat.ui"/>
> <import plugin="org.eclipse.jst.server.websphere.core"/> *[removed after M6]*
> <import plugin="org.eclipse.jst.server.generic.jonas"/>
> <import feature="org.eclipse.jst.server_ui.feature"/>
> <import feature="org.eclipse.jst.server_adapters.feature"/>
> {code}
> And the M7 version of the server_adapters.ext.feature includes these:
> {code}
> <plugin id="org.eclipse.jst.server.tomcat.core"/>
> <plugin id="org.eclipse.jst.server.tomcat.ui"/>
> <plugin id="org.eclipse.jst.server.websphere.core"/>
> <plugin id="org.eclipse.jst.server.generic.jboss"/>
> <plugin id="org.eclipse.jst.server.generic.jonas"/>
> {code}
> So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
> Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
> {code}
> <plugin id="org.eclipse.jst.server.core"/>
> <plugin id="org.eclipse.jst.server.generic.core"/>
> {code}
> [~rob.stryker] WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBDS-2630) include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2630?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2630:
-----------------------------
Description:
Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
[0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
--
Currently, JBDS product feature includes these server adapter plugins & features:
{code}
<import plugin="org.eclipse.jst.server.tomcat.core"/>
<import plugin="org.eclipse.jst.server.tomcat.ui"/>
<import plugin="org.eclipse.jst.server.websphere.core"/>
<import plugin="org.eclipse.jst.server.generic.jonas"/>
<import feature="org.eclipse.jst.server_ui.feature"/>
<import feature="org.eclipse.jst.server_adapters.feature"/>
{code}
And the M7 version of the server_adapters.ext.feature includes these:
{code}
<plugin id="org.eclipse.jst.server.tomcat.core"/>
<plugin id="org.eclipse.jst.server.tomcat.ui"/>
<plugin id="org.eclipse.jst.server.websphere.core"/>
<plugin id="org.eclipse.jst.server.generic.jboss"/>
<plugin id="org.eclipse.jst.server.generic.jonas"/>
{code}
So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
{code}
<plugin id="org.eclipse.jst.server.core"/>
<plugin id="org.eclipse.jst.server.generic.core"/>
{code}
[~rob.stryker] WDYT?
was:
Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
[0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
--
Currently, JBDS product feature includes these server adapter plugins & features:
{code}
<import plugin="org.eclipse.jst.server.tomcat.core"/>
<import plugin="org.eclipse.jst.server.tomcat.ui"/>
<import plugin="org.eclipse.jst.server.websphere.core"/> *[removed after M6]*
<import plugin="org.eclipse.jst.server.generic.jonas"/>
<import feature="org.eclipse.jst.server_ui.feature"/>
<import feature="org.eclipse.jst.server_adapters.feature"/>
{code}
And the M7 version of the server_adapters.ext.feature includes these:
{code}
<plugin id="org.eclipse.jst.server.tomcat.core"/>
<plugin id="org.eclipse.jst.server.tomcat.ui"/>
<plugin id="org.eclipse.jst.server.websphere.core"/>
<plugin id="org.eclipse.jst.server.generic.jboss"/>
<plugin id="org.eclipse.jst.server.generic.jonas"/>
{code}
So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
{code}
<plugin id="org.eclipse.jst.server.core"/>
<plugin id="org.eclipse.jst.server.generic.core"/>
{code}
[~rob.stryker] WDYT?
> include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2630
> URL: https://issues.jboss.org/browse/JBDS-2630
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: P2 Enabled Product
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
> It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
> So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
> [0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
> --
> Currently, JBDS product feature includes these server adapter plugins & features:
> {code}
> <import plugin="org.eclipse.jst.server.tomcat.core"/>
> <import plugin="org.eclipse.jst.server.tomcat.ui"/>
> <import plugin="org.eclipse.jst.server.websphere.core"/>
> <import plugin="org.eclipse.jst.server.generic.jonas"/>
> <import feature="org.eclipse.jst.server_ui.feature"/>
> <import feature="org.eclipse.jst.server_adapters.feature"/>
> {code}
> And the M7 version of the server_adapters.ext.feature includes these:
> {code}
> <plugin id="org.eclipse.jst.server.tomcat.core"/>
> <plugin id="org.eclipse.jst.server.tomcat.ui"/>
> <plugin id="org.eclipse.jst.server.websphere.core"/>
> <plugin id="org.eclipse.jst.server.generic.jboss"/>
> <plugin id="org.eclipse.jst.server.generic.jonas"/>
> {code}
> So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
> Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
> {code}
> <plugin id="org.eclipse.jst.server.core"/>
> <plugin id="org.eclipse.jst.server.generic.core"/>
> {code}
> [~rob.stryker] WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBDS-2630) include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2630?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2630:
-----------------------------
Description:
Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
[0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
--
Currently, JBDS product feature includes these server adapter plugins & features:
{code}
<import plugin="org.eclipse.jst.server.tomcat.core"/>
<import plugin="org.eclipse.jst.server.tomcat.ui"/>
<import plugin="org.eclipse.jst.server.websphere.core"/>
<import plugin="org.eclipse.jst.server.generic.jonas"/>
<import feature="org.eclipse.jst.server_ui.feature"/>
<import feature="org.eclipse.jst.server_adapters.feature"/>
{code}
And the M7 version of the server_adapters.ext.feature includes these:
{code}
<plugin id="org.eclipse.jst.server.tomcat.core"/>
<plugin id="org.eclipse.jst.server.tomcat.ui"/>
<plugin id="org.eclipse.jst.server.websphere.core"/> *[removed]*
<plugin id="org.eclipse.jst.server.generic.jboss"/>
<plugin id="org.eclipse.jst.server.generic.jonas"/>
{code}
So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
{code}
<plugin id="org.eclipse.jst.server.core"/>
<plugin id="org.eclipse.jst.server.generic.core"/>
{code}
[~rob.stryker] WDYT?
was:
Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
[0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
[2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
--
Currently, JBDS product feature includes these server adapter plugins & features:
{code}
<import plugin="org.eclipse.jst.server.tomcat.core"/>
<import plugin="org.eclipse.jst.server.tomcat.ui"/>
<import plugin="org.eclipse.jst.server.websphere.core"/>
<import plugin="org.eclipse.jst.server.generic.jonas"/>
<import feature="org.eclipse.jst.server_ui.feature"/>
<import feature="org.eclipse.jst.server_adapters.feature"/>
{code}
And the M7 version of the server_adapters.ext.feature includes these:
{code}
<plugin id="org.eclipse.jst.server.tomcat.core"/>
<plugin id="org.eclipse.jst.server.tomcat.ui"/>
<plugin id="org.eclipse.jst.server.websphere.core"/>
<plugin id="org.eclipse.jst.server.generic.jboss"/>
<plugin id="org.eclipse.jst.server.generic.jonas"/>
{code}
So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
{code}
<plugin id="org.eclipse.jst.server.core"/>
<plugin id="org.eclipse.jst.server.generic.core"/>
{code}
[~rob.stryker] WDYT?
> include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2630
> URL: https://issues.jboss.org/browse/JBDS-2630
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: P2 Enabled Product
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
> It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
> So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
> [0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
> --
> Currently, JBDS product feature includes these server adapter plugins & features:
> {code}
> <import plugin="org.eclipse.jst.server.tomcat.core"/>
> <import plugin="org.eclipse.jst.server.tomcat.ui"/>
> <import plugin="org.eclipse.jst.server.websphere.core"/>
> <import plugin="org.eclipse.jst.server.generic.jonas"/>
> <import feature="org.eclipse.jst.server_ui.feature"/>
> <import feature="org.eclipse.jst.server_adapters.feature"/>
> {code}
> And the M7 version of the server_adapters.ext.feature includes these:
> {code}
> <plugin id="org.eclipse.jst.server.tomcat.core"/>
> <plugin id="org.eclipse.jst.server.tomcat.ui"/>
> <plugin id="org.eclipse.jst.server.websphere.core"/> *[removed]*
> <plugin id="org.eclipse.jst.server.generic.jboss"/>
> <plugin id="org.eclipse.jst.server.generic.jonas"/>
> {code}
> So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
> Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
> {code}
> <plugin id="org.eclipse.jst.server.core"/>
> <plugin id="org.eclipse.jst.server.generic.core"/>
> {code}
> [~rob.stryker] WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBDS-2630) include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2630?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2630:
-----------------------------
Summary: include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7) (was: include org.eclipse.jst.server_adapters.ext.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin since plugin no longer exists in WTP 3.5M7)
> include org.eclipse.jst.server_adapters.ext.feature and org.eclipse.jst.server_core.feature in JBDS instead of org.eclipse.jst.server.websphere.core plugin (since no longer exists in WTP 3.5M7)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2630
> URL: https://issues.jboss.org/browse/JBDS-2630
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: P2 Enabled Product
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta1
>
>
> Looks like org.eclipse.jst.server.websphere.core_1.0.302.v20080620.jar was removed from WTP after 3.5M6 [0,1]
> It used to be part of org.eclipse.jst.server_adapters.ext.feature_3.3.103.v20130312_1615-67CFHvBgJ9Bc9WGMFHKI8.jar
> So, I propose we include org.eclipse.jst.server_adapters.ext.feature in com.jboss.jbds.product.feature/feature.xml [2] instead of an itemized list of server adapter plugins.
> [0] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [1] http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5....
> [2] https://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jb...
> --
> Currently, JBDS product feature includes these server adapter plugins & features:
> {code}
> <import plugin="org.eclipse.jst.server.tomcat.core"/>
> <import plugin="org.eclipse.jst.server.tomcat.ui"/>
> <import plugin="org.eclipse.jst.server.websphere.core"/>
> <import plugin="org.eclipse.jst.server.generic.jonas"/>
> <import feature="org.eclipse.jst.server_ui.feature"/>
> <import feature="org.eclipse.jst.server_adapters.feature"/>
> {code}
> And the M7 version of the server_adapters.ext.feature includes these:
> {code}
> <plugin id="org.eclipse.jst.server.tomcat.core"/>
> <plugin id="org.eclipse.jst.server.tomcat.ui"/>
> <plugin id="org.eclipse.jst.server.websphere.core"/>
> <plugin id="org.eclipse.jst.server.generic.jboss"/>
> <plugin id="org.eclipse.jst.server.generic.jonas"/>
> {code}
> So this change would remove the missing websphere.core plugin in favour of the generic.jboss plugin.
> Also wondering if we should include org.eclipse.jst.server_core.feature in addition to org.eclipse.jst.server_ui.feature, which would bring in these two extra plugins:
> {code}
> <plugin id="org.eclipse.jst.server.core"/>
> <plugin id="org.eclipse.jst.server.generic.core"/>
> {code}
> [~rob.stryker] WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month