[JBoss JIRA] (JBIDE-16265) JPA validation reports Strategy class "uuid2" could not be found
by Jim Boettcher (JIRA)
Jim Boettcher created JBIDE-16265:
-------------------------------------
Summary: JPA validation reports Strategy class "uuid2" could not be found
Key: JBIDE-16265
URL: https://issues.jboss.org/browse/JBIDE-16265
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.1.1.CR1
Reporter: Jim Boettcher
Priority: Minor
An Entity class with the following:
@Id
@GeneratedValue(generator = "system-uuid")
@GenericGenerator(name = "system-uuid", strategy = "uuid2")
@Column(name = "id", unique = true)
private UUID id;
gives the error:
Strategy class "uuid2" could not be found
changing the strategy to "uuid" will clear the error.
My Project Facet has JPA 2.0
The JPA configuration has:
Platform: Hibernate (JPA 2.0)
JPA implementation:
Disable Library Configuration
the Hibernate jars are on the project classpath
--
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, 4 months
[JBoss JIRA] (JBIDE-16219) Errors about Hibernate console configuration, with no easy way to resolve
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16219?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-16219:
------------------------------
Fix Version/s: 4.2.0.Alpha2
> Errors about Hibernate console configuration, with no easy way to resolve
> -------------------------------------------------------------------------
>
> Key: JBIDE-16219
> URL: https://issues.jboss.org/browse/JBIDE-16219
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Environment: JBDS 7.0.1.GA
> Reporter: Pete Muir
> Fix For: 4.2.0.Alpha2
>
> Attachments: kitchensink-angularjs-bad.zip, kitchensink-angularjs-good.zip
>
>
> In my case, this appears to be caused by existing dot-files (which were created by a previous version of JBDS, on Maven Import...). Removing those files and reimporting fixes the problem.
> I haven't tested whether newer dot-files will cause the problem, or not.
> Attached are two projects, one which shows the problem, and one that doesn't (clean dot-files generated).
--
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, 4 months
[JBoss JIRA] (JBIDE-16264) @PathParam with hyphen in value shows as JAX-RS error
by Jim Boettcher (JIRA)
Jim Boettcher created JBIDE-16264:
-------------------------------------
Summary: @PathParam with hyphen in value shows as JAX-RS error
Key: JBIDE-16264
URL: https://issues.jboss.org/browse/JBIDE-16264
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.1.CR1
Reporter: Jim Boettcher
Priority: Minor
if I have a method like:
@GET
@Path("/rule/{rule-file-name}")
public byte[] getRuleSet(@PathParam("rule-file-name") String ruleSetName)
I get the error:
@PathParam value 'rule-file-name' does not match any @Path annotation template parameters of the java method and the enclosing java type.
If I remove the hyphens from "rule-file-name" the error goes away.
However the hyphen should be allowed.
--
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, 4 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2727:
-----------------------------------
Brian, at the end of the cheatsheet, the Java EE Web project is referenced, it should be the Richfaces Project
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
> Key: JBDS-2727
> URL: https://issues.jboss.org/browse/JBDS-2727
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 7.1.0.GA
>
> Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations
--
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, 4 months
[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ]
Brian Leathem commented on JBDS-2727:
-------------------------------------
I've created a RichFaces cheatsheet here: https://github.com/richfaces/jdf-quickstarts/blob/master/kitchensink-rf/....
> Cheatsheets for JBoss Central archetypes
> ----------------------------------------
>
> Key: JBDS-2727
> URL: https://issues.jboss.org/browse/JBDS-2727
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 7.1.0.GA
>
> Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md
>
>
> Our archetypes should have cheatsheets when imported/opened into eclipse.
> Priority
> 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim
> 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java
> Basically walk the user through the flow of events (from the UI to the backend) in the application
> 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations
--
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, 4 months
[JBoss JIRA] (JBIDE-16238) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Forge]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16238?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-16238.
-----------------------------
Assignee: Koen Aers
Resolution: Done
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Forge]
> ----------------------------------------------------
>
> Key: JBIDE-16238
> URL: https://issues.jboss.org/browse/JBIDE-16238
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [Forge]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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, 4 months
[JBoss JIRA] (JBIDE-15717) Forge 2 console view fails to open
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15717?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-15717.
-------------------------------
Resolution: Done
The F2 console opens correctly. However, a lot more work needs to be done for the functionality to be available in a correct way. This is tracked with JBIDE-16263.
> Forge 2 console view fails to open
> ----------------------------------
>
> Key: JBIDE-15717
> URL: https://issues.jboss.org/browse/JBIDE-15717
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Alpha1
> Environment: Win 7-64, OSX 10.7, Eclipse Java EE Kepler SR1. Installed forge plugins :
> org.jboss.tools.forge.core (1.3.0.Alpha1-v20130927-1755-B403) "Forge Core Plugin" [Active]
> org.jboss.tools.forge.core.ext (1.1.0.Alpha1-v20130927-1755-B403) "Forge Core Extensions Plugin" [Active]
> org.jboss.tools.forge.runtime (1.4.1.Alpha1-v20130927-1755-B403) "Forge Runtime Plugin" [Resolved]
> org.jboss.tools.forge.runtime.ext (1.3.0.Alpha1-v20130927-1755-B403) "Forge Runtime Extensions Plugin" [Resolved]
> org.jboss.tools.forge.ui (1.3.0.Alpha1-v20130927-1755-B403) "Forge UI Plugin" [Active]
> org.jboss.tools.forge.ui.ext (1.1.0.Alpha1-v20130927-1755-B403) "Forge UI Extensions Plugin" [Active]
> org.jboss.tools.forge.ui.notifications (1.1.0.Alpha1-v20130927-1755-B403) "Forge Notifications" [Starting]
> org.jboss.tools.forge.ui.wizards (1.1.0.Alpha1-v20130927-1755-B403) "Forge Wizards" [Starting]
> org.jboss.tools.forge2.runtime (2.0.1.Alpha1-v20130927-1755-B403) "Forge2 Runtime Plugin" [Resolved]
>
> Reporter: Fred Bricon
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
>
> When opening the F2 console view, it fails to open and displays the following error message :
> {noformat}
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.shell.ShellFactory] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:93)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:69)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_fcba2423-6aaa-422e-ac6e-d36b35a7a266.get(Imported_$$_javassist_fcba2423-6aaa-422e-ac6e-d36b35a7a266.java)
> at org.jboss.tools.forge.ext.core.FurnaceService.lookup(FurnaceService.java:87)
> at org.jboss.tools.forge.ui.ext.cli.F2Console.createConsole(F2Console.java:16)
> at org.jboss.tools.aesh.core.console.AeshConsole.initialize(AeshConsole.java:34)
> at org.jboss.tools.aesh.core.console.AeshConsole.<init>(AeshConsole.java:29)
> at org.jboss.tools.forge.ui.ext.cli.F2Console.<init>(F2Console.java:11)
> at org.jboss.tools.forge.ui.ext.cli.F2TextViewer.initializeConsole(F2TextViewer.java:13)
> at org.jboss.tools.aesh.ui.view.AeshTextViewer.initialize(AeshTextViewer.java:77)
> at org.jboss.tools.aesh.ui.view.AeshTextViewer.<init>(AeshTextViewer.java:53)
> at org.jboss.tools.forge.ui.ext.cli.F2TextViewer.<init>(F2TextViewer.java:9)
> at org.jboss.tools.forge.ui.ext.cli.F2View.createPartControl(F2View.java:15)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:142)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:174)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:323)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:877)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:857)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:119)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:333)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:254)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:102)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:71)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:53)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$6.run(PartRenderingEngine.java:526)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:511)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:61)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:949)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:633)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:735)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:706)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:700)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:685)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.handleEvent(PartRenderingEngine.java:134)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4688)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:205)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:80)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:58)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.UIElementImpl.setToBeRendered(UIElementImpl.java:290)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:574)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:543)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:610)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:590)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:544)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:533)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1026)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1192)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1176)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4077)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4074)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4049)
> at org.eclipse.ui.handlers.ShowViewHandler.openView(ShowViewHandler.java:126)
> at org.eclipse.ui.handlers.ShowViewHandler.openOther(ShowViewHandler.java:99)
> at org.eclipse.ui.handlers.ShowViewHandler.execute(ShowViewHandler.java:67)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> 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.ShowViewMenu$3.run(ShowViewMenu.java:141)
> 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:1057)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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: org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.shell.ShellFactory] could be found in any started addons.
> ... 131 more
> {noformat}
> The forge 2 runtime is installed in <eclipse_home>/plugins, but doesn't show up in the list of available runtimes in the forge preferences (but that may be expected behavior, for all I know).
> Fails on both Win 7 and OSX 10.7
--
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, 4 months