[JBoss JIRA] (JBIDE-13987) Improve project wizards in JBoss Central : Proxy Wizards
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13987?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-13987:
-------------------------------
Attachment: www.tar.gz
Still nothing. Both files (.xml&.jar) in attachment.
> Improve project wizards in JBoss Central : Proxy Wizards
> --------------------------------------------------------
>
> Key: JBIDE-13987
> URL: https://issues.jboss.org/browse/JBIDE-13987
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy, respin-b
> Fix For: 4.1.0.Beta1
>
> Attachments: www.tar.gz
>
>
> The "Start from scratch" section (formerly known as Project section) in JBoss Central needs to support the following requirements :
> - wizard list (label/order/description) must be updateable remotely
> - show wizards (including the proper icon) even if their contributing plugins are missing
> - when clicking on the wizard link in JBoss Central, if the wizard is available then open it, else, install the required plugins
> The general idea here is to use some kind of proxy wizard. A proxy wizard model should have the following attributes :
> - id : the proxy wizard id
> - label : the proxy wizard label shown in JBoss Central
> - wizardId : the real wizard id used by Central to open the wizard dialog
> - iconPath : the path to the wizard icon (independent of required connector)
> - description : the description shown in Central when hovering over the wizard link
> - requiredConnectorIds : the connector ids to install if the real wizard is not available
> - priority : order in which the wizard is displayed in JBoss Central
> The proxy wizards will be declared in the jboss-discovery.jar plugin.xml (to minimize build / maintenance overhead). The jar will also include the required icons.
> The jar will be fetched remotely by the discovery mechanism but a cached version must be kept for offline usage.
--
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
12 years, 10 months
[JBoss JIRA] (JBIDE-13882) Allow users to easily "binary deploy"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13882?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13882:
------------------------------------------
updated label for binary deployment checkbox:
"disable automatic maven build when publishing to OpenShift"
> Allow users to easily "binary deploy"
> -------------------------------------
>
> Key: JBIDE-13882
> URL: https://issues.jboss.org/browse/JBIDE-13882
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta2
>
> Attachments: 2013-05-29 13.33.bmml, 2013-05-29 13.33.bmml, 2013-05-29 13.33.bmml, 2013-05-29 13.33.png
>
>
> We should have an option in the wizard that allows easy "binary only" deployment
> {quote}
> 'binary deployment only' option which will go disable the the build marker...but what do we do about the existing project content - just leave it in place I would say.{quote}
--
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
12 years, 10 months
[JBoss JIRA] (JBIDE-14791) cannot rename deployed modules in AS7 nor Openshift servers
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-14791:
-------------------------------------------
Summary: cannot rename deployed modules in AS7 nor Openshift servers
Key: JBIDE-14791
URL: https://issues.jboss.org/browse/JBIDE-14791
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift, server
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 4.1.0.Beta2
openshift nor as7 seem to anymore be able to rename their deployed modules.
i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in /
--
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
12 years, 10 months
[JBoss JIRA] (JBIDE-12219) A module cannot be properly removed from server by pressing Delete key
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12219?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-12219.
------------------------------
Verified in JBT 4.1.0.Beta1
> A module cannot be properly removed from server by pressing Delete key
> -----------------------------------------------------------------------
>
> Key: JBIDE-12219
> URL: https://issues.jboss.org/browse/JBIDE-12219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta1
>
>
> When you create a Seam 2.2 EAR project and deploy it to EAP 5.1.2 it cannot be properly removed - if you select both the ear and the -ds.xml in the server view and press Delete, they will be first both undeployed, but right after that the ear will be deployed again and will fail to do so without the datasource.
> So the main problem is that even after removing everything from the server, the ear project somehow is still there in the deploy directory.
--
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
12 years, 10 months
[JBoss JIRA] (JBDS-2657) NoClassDefFoundError: org/jboss/tools/common/core/ecf/ECFTransport thrown refreshing JBoss Buzz & tutorials
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2657?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2657:
--------------------------------------
Assignee: Rob Stryker
> NoClassDefFoundError: org/jboss/tools/common/core/ecf/ECFTransport thrown refreshing JBoss Buzz & tutorials
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2657
> URL: https://issues.jboss.org/browse/JBDS-2657
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Rob Stryker
>
> 0. Install & launch Eclipse Kepler JEE RC2 bundle from http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/...
> {code}
> workspace=/home/nboldt/eclipse/workspace-clean43
> target=/home/nboldt/eclipse/43clean
> eclipse=/home/nboldt/tmp/Eclipse_Bundles/eclipse-jee-kepler-RC2-linux-gtk-x86_64.tar.gz
> cd ${target}
> tar xzf $eclipse
> ${target}/eclipse/eclipse -clean -showLocation -data $workspace -consolelog -console -vm /opt/sun-java2-7.0/bin/java -vmargs -Xms128M -Xmx256M -XX:PermSize=128M -XX:MaxPermSize=256M $1 2>&1 | tee "logs/eclipse.log.`date`.txt"
> {code}
> 1. Install JBDS "BYOE" or "Core Features" feature from the Beta1 installer jar from https://devstudio.jboss.com/earlyaccess/7.0.0.Beta1.html (see instructions under "Update Site Zip")
> 2. On startup of JBDS Central, the following problems are logged to console:
> {code}
> !ENTRY org.jboss.tools.project.examples 4 0 2013-06-06 22:34:44.892
> !MESSAGE java.lang.NoClassDefFoundError: org/jboss/tools/common/core/ecf/ECFTransport
> !STACK 0
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: org/jboss/tools/common/core/ecf/ECFTransport
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
> at java.util.concurrent.FutureTask.get(FutureTask.java:111)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:347)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:310)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:53)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/tools/common/core/ecf/ECFTransport
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjectExamplesFile(ProjectExampleUtil.java:779)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil$FetchProjectExampleDocumentTask.call(ProjectExampleUtil.java:937)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil$FetchProjectExampleDocumentTask.call(ProjectExampleUtil.java:1)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.tools.common.core.ecf.ECFTransport cannot be found by org.jboss.tools.project.examples_1.5.0.Beta2-v20130605-2021-B325
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 11 more
> !ENTRY org.eclipse.core.jobs 4 2 2013-06-06 22:34:44.924
> !MESSAGE An internal error occurred during: "Refreshing JBoss Buzz...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/jboss/tools/common/core/ecf/ECFTransport
> at org.jboss.tools.central.jobs.AbstractRefreshJob.getUrlModified(AbstractRefreshJob.java:284)
> at org.jboss.tools.central.jobs.AbstractRefreshJob.run(AbstractRefreshJob.java:204)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.jboss.tools.common.core.ecf.ECFTransport cannot be found by org.jboss.tools.central_1.2.0.Beta2-v20130605-2021-B325
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 3 more
> !ENTRY org.eclipse.core.jobs 4 2 2013-06-06 22:34:44.996
> !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/jboss/tools/common/core/ecf/ECFTransport
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjectExamplesFile(ProjectExampleUtil.java:779)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.handleCategories(ProjectExampleUtil.java:556)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:503)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:310)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:53)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
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
12 years, 10 months
[JBoss JIRA] (JBIDE-14790) Unable to create Seam Web Project
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-14790:
----------------------------------
Summary: Unable to create Seam Web Project
Key: JBIDE-14790
URL: https://issues.jboss.org/browse/JBIDE-14790
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.1.0.Beta1
Environment: JBT 4.1.0.Beta1 installed from eclipse marketplace
Reporter: Radim Hopp
Fix For: 4.1.0.Beta2
I'm unable to create Seam Web Project (File->New->Other->Seam->Seam Web Project)
This exception appears immediately, when New Seam Project wizard is shown:
{noformat}
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.seam.ui.internal.project.facet.SeamInstallWizardPage)
at org.eclipse.swt.SWT.error(SWT.java:4397)
at org.eclipse.swt.SWT.error(SWT.java:4312)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
at org.eclipse.jface.window.Window.open(Window.java:802)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85)
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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
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:3742)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
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)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.seam.ui.internal.project.facet.SeamInstallWizardPage
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at java.lang.Class.newInstance0(Class.java:374)
at java.lang.Class.newInstance(Class.java:327)
at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.create(ProjectFacetsUiManagerImpl.java:170)
at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.getWizardPages(ProjectFacetsUiManagerImpl.java:148)
at org.eclipse.wst.common.project.facet.ui.internal.ProjectFacetsUiManagerImpl.getWizardPages(ProjectFacetsUiManagerImpl.java:108)
at org.eclipse.wst.common.project.facet.ui.ProjectFacetsUiManager.getWizardPages(ProjectFacetsUiManager.java:30)
at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.handleSelectedFacetsChangedEvent(ModifyFacetedProjectWizard.java:712)
at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.access$0(ModifyFacetedProjectWizard.java:670)
at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$1$1.run(ModifyFacetedProjectWizard.java:166)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 51 more
{noformat}
And this one when clicking on Finish button:
{noformat}
java.lang.NullPointerException
at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:340)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
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:3742)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
at org.eclipse.jface.window.Window.open(Window.java:802)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:259)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:85)
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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:165)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
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:3742)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1109)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
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)
{noformat}
--
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
12 years, 10 months
[JBoss JIRA] (JBIDE-13987) Improve project wizards in JBoss Central : Proxy Wizards
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13987?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-13987:
-------------------------------------
try <entry url="http://localhost/org.jboss.tools.central.discovery.jar" permitCategories="true"/>
> Improve project wizards in JBoss Central : Proxy Wizards
> --------------------------------------------------------
>
> Key: JBIDE-13987
> URL: https://issues.jboss.org/browse/JBIDE-13987
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Labels: new_and_noteworthy, respin-b
> Fix For: 4.1.0.Beta1
>
>
> The "Start from scratch" section (formerly known as Project section) in JBoss Central needs to support the following requirements :
> - wizard list (label/order/description) must be updateable remotely
> - show wizards (including the proper icon) even if their contributing plugins are missing
> - when clicking on the wizard link in JBoss Central, if the wizard is available then open it, else, install the required plugins
> The general idea here is to use some kind of proxy wizard. A proxy wizard model should have the following attributes :
> - id : the proxy wizard id
> - label : the proxy wizard label shown in JBoss Central
> - wizardId : the real wizard id used by Central to open the wizard dialog
> - iconPath : the path to the wizard icon (independent of required connector)
> - description : the description shown in Central when hovering over the wizard link
> - requiredConnectorIds : the connector ids to install if the real wizard is not available
> - priority : order in which the wizard is displayed in JBoss Central
> The proxy wizards will be declared in the jboss-discovery.jar plugin.xml (to minimize build / maintenance overhead). The jar will also include the required icons.
> The jar will be fetched remotely by the discovery mechanism but a cached version must be kept for offline usage.
--
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
12 years, 10 months