[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 reassigned JBDS-2630:
--------------------------------
Assignee: Rob Stryker (was: Nick Boldt)
In the mean time I've removed the offending plugin, but we can still consider adding the other feature(s) instead. If you don't want or need 'em, then just mark this resolved or closed.
> 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: Rob Stryker
> 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] (JBIDE-14356) GC overhead limit exceeded when adding fileset to LiveReload Server
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14356?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14356:
----------------------------------------
Labels: newandnoteworthy (was: )
> 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: Bug
> Components: livereload
> Reporter: Stian Thorgersen
> Assignee: Rob Stryker
> Labels: newandnoteworthy
> Fix For: 4.1.0.Beta1
>
>
> 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-12962) JBoss Central - Create Projects - Future Archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12962?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-12962 at 5/16/13 6:14 AM:
--------------------------------------------------------------
This has been fixed as part of JBIDE-13987. New wizards can be dynamically added to Central (outside the regular JBT/JBDS lifecycle).
In order to contribute new wizards to JBoss Central, you need to add a new <proxyWizard> extension in com.jboss.jbds.central.discovery/plugin.xml (for JBDS) and/or org.jboss.tools.central.discovery/plugin.xml for JBT, like :
{code}
<extension point="org.jboss.tools.central.proxyWizard">
...
<proxyWizard
id="openshift.wizard"
description="%openshift.wizard.description"
label="OpenShift Application"
priority="2"
iconPath="images/wizards/openshift-logo-white-icon.png"
wizardId="org.jboss.ide.eclipse.as.openshift.express.ui.wizard.createNewApplicationWizard"
requiredComponentIds="org.jboss.tools.openshift.feature">
</proxyWizard>
</extension>
{code}
* Your features need to be available as discovery connectors in the same plugin.xml and listed as requiredComponentIds
* Your wizard (referenced by wizardId) doesn't need to be maven-based
* Icons for the wizards need to be added under com.jboss.jbds.central.discovery/images/wizards and org.jboss.tools.central.discoveryimages/wizards
was (Author: fbricon):
This has been fixed as part of JBIDE-13987. New wizards can be dynamically added to Central (outside the regular JBT/JBDS lifecycle).
In order to contribute new wizards to JBoss Central, you need to add a new <proxyWizard> extension in com.jboss.jbds.central.discovery/plugin.xml (for JBDS) and/or org.jboss.tools.central.discovery/plugin.xml for JBT
<extension point="org.jboss.tools.central.proxyWizard">
...
<proxyWizard
id="openshift.wizard"
description="%openshift.wizard.description"
label="OpenShift Application"
priority="2"
iconPath="images/wizards/openshift-logo-white-icon.png"
wizardId="org.jboss.ide.eclipse.as.openshift.express.ui.wizard.createNewApplicationWizard"
requiredComponentIds="org.jboss.tools.openshift.feature">
</proxyWizard>
</extension>
* Your features need to be available as discovery connectors in the same plugin.xml and listed as requiredComponentIds
* Your wizard (referenced by wizardId) doesn't need to be maven-based
* Icons for the wizards need to be added under com.jboss.jbds.central.discovery/images/wizards and org.jboss.tools.central.discoveryimages/wizards
> JBoss Central - Create Projects - Future Archetypes
> ---------------------------------------------------
>
> Key: JBIDE-12962
> URL: https://issues.jboss.org/browse/JBIDE-12962
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.0.0.Alpha2
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 4.1.0.Beta1
>
> Attachments: Screen Shot 2012-11-01 at 6.13.27 PM.png, Screen Shot 2012-11-01 at 6.14.08 PM.png
>
>
> Currently JBoss Central's Create Projects section includes the following:
> 1) Dynamic Web Project
> 2) OpenShift Application
> 3) Java EE Web Project
> 4) Java EE Project (Java EE EAR Project)
> 5) HTML5 Project
> 6) RichFaces Project
> 7) SpringMVC Project
> 8) GWT Web Project
> And in 2013 we can expect at least the following potential archetypes to be created:
> - Portal/Gatein Project
> - EDS/Teiid Project
> - SOA/Switchyard Project
> - BRMS/jBPM/BPMN2 Project
> - BRMS/Drools Expert Project
> - Fuse/Camel Project
> These additional archetypes would only need to be available when the end-user has:
> a) acquired the additional tools (JBoss Central - Software/Update tab)
> b) potentially switched to the correct Perspective
> This jira represents the "design" discussion.
--
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-12962) JBoss Central - Create Projects - Future Archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12962?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-12962.
---------------------------------
Resolution: Done
This has been fixed as part of JBIDE-13987. New wizards can be dynamically added to Central (outside the regular JBT/JBDS lifecycle).
In order to contribute new wizards to JBoss Central, you need to add a new <proxyWizard> extension in com.jboss.jbds.central.discovery/plugin.xml (for JBDS) and/or org.jboss.tools.central.discovery/plugin.xml for JBT
<extension point="org.jboss.tools.central.proxyWizard">
...
<proxyWizard
id="openshift.wizard"
description="%openshift.wizard.description"
label="OpenShift Application"
priority="2"
iconPath="images/wizards/openshift-logo-white-icon.png"
wizardId="org.jboss.ide.eclipse.as.openshift.express.ui.wizard.createNewApplicationWizard"
requiredComponentIds="org.jboss.tools.openshift.feature">
</proxyWizard>
</extension>
* Your features need to be available as discovery connectors in the same plugin.xml and listed as requiredComponentIds
* Your wizard (referenced by wizardId) doesn't need to be maven-based
* Icons for the wizards need to be added under com.jboss.jbds.central.discovery/images/wizards and org.jboss.tools.central.discoveryimages/wizards
> JBoss Central - Create Projects - Future Archetypes
> ---------------------------------------------------
>
> Key: JBIDE-12962
> URL: https://issues.jboss.org/browse/JBIDE-12962
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.0.0.Alpha2
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 4.1.0.Beta1
>
> Attachments: Screen Shot 2012-11-01 at 6.13.27 PM.png, Screen Shot 2012-11-01 at 6.14.08 PM.png
>
>
> Currently JBoss Central's Create Projects section includes the following:
> 1) Dynamic Web Project
> 2) OpenShift Application
> 3) Java EE Web Project
> 4) Java EE Project (Java EE EAR Project)
> 5) HTML5 Project
> 6) RichFaces Project
> 7) SpringMVC Project
> 8) GWT Web Project
> And in 2013 we can expect at least the following potential archetypes to be created:
> - Portal/Gatein Project
> - EDS/Teiid Project
> - SOA/Switchyard Project
> - BRMS/jBPM/BPMN2 Project
> - BRMS/Drools Expert Project
> - Fuse/Camel Project
> These additional archetypes would only need to be available when the end-user has:
> a) acquired the additional tools (JBoss Central - Software/Update tab)
> b) potentially switched to the correct Perspective
> This jira represents the "design" discussion.
--
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] (TOOLSDOC-318) NeedInfo: Describing the software listed on Software/Update page
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-318?page=com.atlassian.jira.plug... ]
Max Rydahl Andersen commented on TOOLSDOC-318:
----------------------------------------------
Nothing planned for this release no.
> NeedInfo: Describing the software listed on Software/Update page
> ----------------------------------------------------------------
>
> Key: TOOLSDOC-318
> URL: https://issues.jboss.org/browse/TOOLSDOC-318
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Max Rydahl Andersen
>
> Software is listed in the JBoss Central tab, on the Software/Update page. This is not all of the software available to install in Eclipse so why are these specific items listed here? How do I describe them to a user? Are they JBoss plug-ins or related to JBoss technology or ...?
> Also, is the software/update page also going to be updated for JBDS 7.0? I can see that the Getting Started page is undergoing redevelopment.
--
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-14333) have context sensitive parameterized commands for open file, show type etc. with proper API
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14333?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14333:
---------------------------------------------
variable substitution from where ? Eclipse global variables ? should be possible to register a "cheatsheet.project" variable here would it not ? But for now {project} is probably fine.
What does "profile" refer to for launchJunitTest ? junit doesn't sound like something to know about maven nor arquillian...
Can you point me to do api/docs for what you are making here ?
btw. the old actions will still work, right? these are *additional* commands, correct?
> have context sensitive parameterized commands for open file, show type etc. with proper API
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-14333
> URL: https://issues.jboss.org/browse/JBIDE-14333
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples
> Reporter: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1, 4.1.0.Beta2
>
>
> currently our custom cheatsheet commands requires the project name(s) to be known upfront. We should make them less reliant on project names and if at all possible have the project name calculated based on the project the cheatsheet file is open in.
> The commands should also actually be commands with named parameters so the order of parameters does not matter and we should make sure these have a good and long term API so cheatsheets will continue to work well in the future.
--
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