[JBoss JIRA] (JBIDE-13159) gwt-kitchensink fails to deploy - class not found
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13159?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-13159:
---------------------------------------
@[~mmalina]: GWT configurator doesn't help. What do help is changing OpenJDK 7 to 6.
> gwt-kitchensink fails to deploy - class not found
> -------------------------------------------------
>
> Key: JBIDE-13159
> URL: https://issues.jboss.org/browse/JBIDE-13159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: GWT, maven
> Affects Versions: 4.0.0.CR1
> Environment: JBDS 6.0.0.CR1a B133
> JBT 4.0.0.CR1a B97
> OS X 10.8.2
> Oracle Java 1.7
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta1
>
>
> When you try to deploy the gwt project from Central, it fails to deploy with the following error:
> {code}
> 15:27:18,698 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jboss-gwt-webapp.war in deployment directory. To trigger deployment create a file called jboss-gwt-webapp.war.dodeploy
> 15:27:18,713 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jboss-gwt-webapp.war"
> 15:27:20,830 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for primary
> 15:27:20,978 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
> 15:27:20,979 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.jboss-gwt-webapp.war" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
> 15:27:21,021 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jboss-gwt-webapp.war
> 15:27:21,301 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jboss-gwt-webapp.war
> 15:27:21,332 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
> 15:27:21,364 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011402: Starting Persistence Unit Service 'jboss-gwt-webapp.war#primary'
> 15:27:21,461 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
> 15:27:21,467 INFO [org.hibernate.Version] (MSC service thread 1-1) HHH000412: Hibernate Core {4.0.1.Final}
> 15:27:21,469 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000206: hibernate.properties not found
> 15:27:21,473 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-1) HHH000021: Bytecode provider name : javassist
> 15:27:21,490 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-1) HHH000204: Processing PersistenceUnitInfo [
> name: primary
> ...]
> 15:27:21,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]
> Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/Users/rasp/jbossqa/runtimes/jboss-as-7.1.1.Final/standalone/deployments/jboss-gwt-webapp.war/WEB-INF/classes/
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854)
> at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> Caused by: java.lang.RuntimeException: JBAS011431: Could not load entity class 'org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30' with PersistenceUnitInfo.getClassLoader()
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:175)
> at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:489)
> at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851)
> ... 9 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.errai.marshalling.server.impl.ServerMarshallingFactoryImpl$30 from [Module "deployment.jboss-gwt-webapp.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
> at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getPackagesInJar(HibernateAnnotationScanner.java:171)
> ... 11 more
> 15:27:21,714 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "jboss-gwt-webapp.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}
> 15:27:21,742 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment jboss-gwt-webapp.war in 27ms
> 15:27:21,743 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.persistenceunit."jboss-gwt-webapp.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."jboss-gwt-webapp.war#primary": Failed to start service
> 15:27:21,745 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jboss-gwt-webapp.war#primary\": Failed to start service"}}}}
> {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
11 years, 7 months
[JBoss JIRA] (JBIDE-13415) Report a better error when using wrong project type to create WS Client
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13415?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13415:
-------------------------------------------
This actually has nothing to do with the project type. The problem was with how we were getting the default runtime from the preferences. That has been fixed with the pull request for JBIDE-14339 & JBIDE-14358. Same issue, just hit from a slightly different direction.
> Report a better error when using wrong project type to create WS Client
> -----------------------------------------------------------------------
>
> Key: JBIDE-13415
> URL: https://issues.jboss.org/browse/JBIDE-13415
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Webservices
> Affects Versions: 4.0.0.Final
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Beta1
>
> Attachments: Screenshot_error.png
>
>
> If you try and use a standard Java Project to create WS Client from a WSDL, you get a NPE thrown. But an error stating that the project type expected is a Dynamic Web Project would be much more appropriate.
> !Screenshot_error.png|thumbnail!
--
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
11 years, 7 months
[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13414:
-------------------------------------------
That's interesting. With the most recent code on Kepler, I'm seeing an exception pop up in a dialog:
{code}
Error: Could not import. (use --verbose to see full traces)
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:120)
at org.apache.cxf.tools.common.ToolException.printThrowable(ToolException.java:126)
at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:121)
at org.apache.cxf.tools.common.ToolException.printStackTrace(ToolException.java:104)
at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:291)
at org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:279)
at org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:104)
at org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.modules.Module.run(Module.java:262)
at org.jboss.modules.Main.main(Main.java:329)
{code}
> No Error reported when WS Client code generation fails
> ------------------------------------------------------
>
> Key: JBIDE-13414
> URL: https://issues.jboss.org/browse/JBIDE-13414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Labels: web_service_client
> Fix For: 4.1.0.Beta1
>
> Attachments: echoService.wsdl
>
>
> If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this:
> Failed to invoke WSDLToJava
> org.apache.cxf.tools.common.ToolException: Thrown by JAXB:
> Thrown by JAXB:
> Two declarations cause a collision in the ObjectFactory class.
> ...
> However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is.
--
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
11 years, 7 months
[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-13414:
--------------------------------------
Fix Version/s: 4.1.0.Beta1
> No Error reported when WS Client code generation fails
> ------------------------------------------------------
>
> Key: JBIDE-13414
> URL: https://issues.jboss.org/browse/JBIDE-13414
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Reporter: Mustafa Musaji
> Assignee: Brian Fitzpatrick
> Labels: web_service_client
> Fix For: 4.1.0.Beta1
>
> Attachments: echoService.wsdl
>
>
> If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this:
> Failed to invoke WSDLToJava
> org.apache.cxf.tools.common.ToolException: Thrown by JAXB:
> Thrown by JAXB:
> Two declarations cause a collision in the ObjectFactory class.
> ...
> However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is.
--
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
11 years, 7 months
[JBoss JIRA] (JBIDE-14358) Not able to generate JBOSS WS client code in eclispe Juno
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14358?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-14358:
-------------------------------------------
So the workaround may get you a bit further, but I think I have it knocked out for the next version.
> Not able to generate JBOSS WS client code in eclispe Juno
> ---------------------------------------------------------
>
> Key: JBIDE-14358
> URL: https://issues.jboss.org/browse/JBIDE-14358
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 4.0.0.Final
> Environment: EAP 5.1.0
> Reporter: Roopa Chakra
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Beta1
>
>
> Tried installing JBoss tools (JBoss Tools (Juno) 4.0.1.Final from eclipse market place) to eclipse juno. Set the JBOSS WS run time location by following steps.
>
> Window->Preferences->Web Services->JBossWS Preferences->Add. Then provide a name (eg. jboss-eap-5.1.0), Home Folder should be $JBOSS_HOME (which is the jboss-as folder). JBOSS server is EAP 5.1.0.
> When I right click on existing wsdl to generate client code I get below exception.
> Not sure why tools is not able to find JBOSSWS runtime location.
>
> IWAB0014E Unexpected exception occurred.
>
> java.lang.NullPointerException
> at org.jboss.tools.ws.creation.core.utils.JBossWSCreationUtils.getJBossWSRuntimeLocation(JBossWSCreationUtils.java:296)
> at org.jboss.tools.ws.creation.core.commands.InitialClientCommand.execute(InitialClientCommand.java:62)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:908)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)"
--
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
11 years, 7 months
[JBoss JIRA] (JBTIS-25) SwitchYard 0.5.0 requires Guvnor 5.4, but 5.3 is on the 3.3.x nightly site
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-25?page=com.atlassian.jira.plugin.s... ]
Rob Cernich updated JBTIS-25:
-----------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
> SwitchYard 0.5.0 requires Guvnor 5.4, but 5.3 is on the 3.3.x nightly site
> --------------------------------------------------------------------------
>
> Key: JBTIS-25
> URL: https://issues.jboss.org/browse/JBTIS-25
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: switchyard
> Reporter: Nick Boldt
> Assignee: Rob Cernich
> Fix For: 4.0.0
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> (2012-05-31 11:49:50) nboldt: rcernich: can you install your stuff into a clean eclipse instance from here? http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/3.3.x.Ni...
> (2012-05-31 11:50:19) nboldt: rcernich: contains SY 0.5.0.v20120530-0222-H91-CI
> (2012-05-31 11:50:41) nboldt: should be able to resolve ALL your upstream needs, from eclipse.org, m2e, jboss.org, etc.
> (2012-05-31 11:50:12) rcernich: nboldt: pretty sure
> (2012-05-31 11:50:42) rcernich: nboldt: dependencies are mostly limited to m2e, emf, wtp
> (2012-05-31 11:50:57) rcernich: nboldt: jboss m2e is optional
> (2012-05-31 11:51:16) rcernich: nboldt: we have some features waiting in the wings for guvnor integration
> (2012-05-31 11:51:26) rcernich: nboldt: but that requires guvnor 5.4 tools
> (2012-05-31 12:33:50) nboldt: rcernich: looks like we're pulling 5.3.2 into SOA Tooling https://hudson.qa.jboss.com/hudson/view/SOA-Team/view/SOATools-3.3.0/job/...
> (2012-05-31 12:35:16) nboldt: if you need 5.4 droolsjbpm stuff in soa tooling site so it's available when installing switchyard 0.5.0, then ... this is a problem and you need to get Doug on it.
> (2012-05-31 12:36:15) nboldt: https://repository.jboss.org/nexus/content/groups/public/org/drools/org.d... is out
> If I understand the issue, you want to include SY 0.5.0 in SOATools 3.3.0.Beta3, but that requires Guvnor 5.4.0.Final, which is not as yet being aggregated.
> Integrate http://download.jboss.org/drools/release/5.4.0.Final/org.drools.updatesite/ into the staging composite site [1] for SOA Tooling 3.3.x.Nightly instead of the 5.3.2 bits.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
--
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
11 years, 7 months