[JBoss JIRA] (LOCUS-52) Make jaxb-xjc Java 11 compatible
by Aurélien Pupier (Jira)
Aurélien Pupier created LOCUS-52:
------------------------------------
Summary: Make jaxb-xjc Java 11 compatible
Key: LOCUS-52
URL: https://issues.jboss.org/browse/LOCUS-52
Project: JBoss Tools Locus
Issue Type: Feature Request
Affects Versions: 1.7.0
Reporter: Aurélien Pupier
jaxb-xjc requires javax.xml.bind which has been removed from JRE
I think the bundle needs to define it as import package explicitly in the MANIFEST.MF
The xjc 2.2.7 version used also have this issue (was released in 2013 so seems normal)
The xjc 2.3.1 latest version is defining a lot of import package. I guess all of them would need to be added.
Should we create a new version 2.3.1 of jboss tools locus? or update the 2.2.7 MANIFEST.MF? or both?
I spotted the issue with this error when using Fuse Tooling:
{noformat}
!ENTRY org.jboss.tools.fuse.transformation.editor 4 0 2018-10-10 14:09:46.830
!MESSAGE Error performing finish
!STACK 0
java.lang.reflect.InvocationTargetException
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:451)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:356)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:977)
at org.jboss.tools.fuse.transformation.editor.wizards.NewTransformationWizard.performFinish(NewTransformationWizard.java:329)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:775)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:414)
at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:622)
at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:84)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4145)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1055)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3958)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3561)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:821)
at org.eclipse.jface.window.Window.open(Window.java:797)
at org.jboss.tools.fuse.transformation.extensions.DataMapperEndpointFigureFeature.createNode(DataMapperEndpointFigureFeature.java:50)
at org.fusesource.ide.camel.editor.features.create.ext.CreateFigureFeature.create(CreateFigureFeature.java:347)
at org.fusesource.ide.camel.editor.features.create.ext.CreateEndpointFigureFeature.create(CreateEndpointFigureFeature.java:95)
at org.eclipse.graphiti.features.impl.AbstractCreateFeature.execute(AbstractCreateFeature.java:100)
at org.eclipse.graphiti.internal.command.GenericFeatureCommandWithContext.execute(GenericFeatureCommandWithContext.java:64)
at org.eclipse.graphiti.internal.command.GFPreparableCommand.doExecute(GFPreparableCommand.java:37)
at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
at org.eclipse.graphiti.ui.internal.editor.GFWorkspaceCommandStackImpl.execute(GFWorkspaceCommandStackImpl.java:128)
at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
at org.eclipse.graphiti.internal.command.CommandExec.executeCommand(CommandExec.java:85)
at org.eclipse.graphiti.ui.internal.command.CreateModelObjectCommand.execute(CreateModelObjectCommand.java:49)
at org.eclipse.graphiti.ui.internal.editor.EmfOnGefCommand.execute(EmfOnGefCommand.java:54)
at org.eclipse.graphiti.internal.command.GFPreparableCommand2.doExecute(GFPreparableCommand2.java:43)
at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
at org.eclipse.emf.workspace.EMFCommandOperation.doExecute(EMFCommandOperation.java:119)
at org.eclipse.emf.workspace.AbstractEMFOperation.execute(AbstractEMFOperation.java:150)
at org.eclipse.core.commands.operations.DefaultOperationHistory.execute(DefaultOperationHistory.java:491)
at org.eclipse.emf.workspace.impl.WorkspaceCommandStackImpl.doExecute(WorkspaceCommandStackImpl.java:208)
at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
at org.eclipse.graphiti.ui.internal.editor.GFWorkspaceCommandStackImpl.execute(GFWorkspaceCommandStackImpl.java:97)
at org.eclipse.graphiti.ui.internal.editor.GFCommandStack.execute(GFCommandStack.java:139)
at org.eclipse.gef.tools.AbstractTool.executeCommand(AbstractTool.java:425)
at org.eclipse.gef.tools.AbstractTool.executeCurrentCommand(AbstractTool.java:438)
at org.eclipse.gef.tools.CreationTool.performCreation(CreationTool.java:269)
at org.eclipse.gef.tools.CreationTool.handleButtonUp(CreationTool.java:189)
at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200)
at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301)
at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380)
at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:224)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4145)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1055)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3958)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3561)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:628)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:199)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
at org.eclipse.equinox.launcher.Main.main(Main.java:1474)
Caused by: java.lang.NoClassDefFoundError: javax/xml/bind/ValidationEventLocator
at com.sun.tools.xjc.reader.internalizer.DOMForestScanner.scan(DOMForestScanner.java:84)
at com.sun.tools.xjc.reader.internalizer.DOMForestScanner.scan(DOMForestScanner.java:100)
at com.sun.tools.xjc.reader.internalizer.DOMForestParser.parse(DOMForestParser.java:104)
at com.sun.tools.xjc.reader.internalizer.DOMForest$2.parse(DOMForest.java:517)
at java.xml/org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:357)
at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSchemaDocument(XSDHandler.java:2305)
at java.xml/com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:574)
at java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:617)
at java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:576)
at java.xml/com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:542)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:276)
at com.sun.tools.xjc.reader.internalizer.DOMForest.weakSchemaCorrectnessCheck(DOMForest.java:489)
at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:260)
at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:95)
at org.jboss.tools.fuse.transformation.core.model.xml.XmlModelGenerator.generateFromSchema(XmlModelGenerator.java:378)
at org.jboss.tools.fuse.transformation.core.model.xml.XmlModelGenerator.generateFromInstance(XmlModelGenerator.java:313)
at org.jboss.tools.fuse.transformation.editor.wizards.NewTransformationWizard.generateModel(NewTransformationWizard.java:462)
at org.jboss.tools.fuse.transformation.editor.wizards.NewTransformationWizard.access$1(NewTransformationWizard.java:400)
at org.jboss.tools.fuse.transformation.editor.wizards.NewTransformationWizard$1.run(NewTransformationWizard.java:250)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:440)
... 72 more
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.ValidationEventLocator cannot be found by org.jboss.tools.locus.jaxb-core_2.2.7.v20160127-1545
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 92 more
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25000:
------------------------------------
[~adietish] can you check that this is the same as JBIDE-26408: when the pod is running in debug mode, check that node is running with --inspect instead of --debug
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: openshift_v3, server_adapter
> Fix For: 4.10.0.AM1
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26088) arbitrary folder should not be able to be searched for runtimes
by Denis Golovin (Jira)
[ https://issues.jboss.org/browse/JBIDE-26088?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-26088:
---------------------------------------
[~rob.stryker] Is this still relevant?
> arbitrary folder should not be able to be searched for runtimes
> ---------------------------------------------------------------
>
> Key: JBIDE-26088
> URL: https://issues.jboss.org/browse/JBIDE-26088
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-server-protocol
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Major
>
> Server currently has following interface / json entry point:
> CompletableFuture<List<ServerBean>> findServerBeans(DiscoveryPath path);
> However, any arbitrary system path can be searched this way. It'd be better if any discovery path had to be kept in the model via addDiscoveryPath first, to ensure that the server isn't somehow restricted from searching various paths.
> Of course right now there's no API or configuration file to actually restrict scanning various folders, but I would imagine that eventually such restrictions would be made such that the void addDiscoveryPath(DiscoveryPath path); entrypoint could restrict or reject additions.
> I believe [~dgolovin] disagrees with this approach. Please discuss.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26088) arbitrary folder should not be able to be searched for runtimes
by Denis Golovin (Jira)
[ https://issues.jboss.org/browse/JBIDE-26088?page=com.atlassian.jira.plugi... ]
Denis Golovin reassigned JBIDE-26088:
-------------------------------------
Assignee: Rob Stryker
> arbitrary folder should not be able to be searched for runtimes
> ---------------------------------------------------------------
>
> Key: JBIDE-26088
> URL: https://issues.jboss.org/browse/JBIDE-26088
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-server-protocol
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Major
>
> Server currently has following interface / json entry point:
> CompletableFuture<List<ServerBean>> findServerBeans(DiscoveryPath path);
> However, any arbitrary system path can be searched this way. It'd be better if any discovery path had to be kept in the model via addDiscoveryPath first, to ensure that the server isn't somehow restricted from searching various paths.
> Of course right now there's no API or configuration file to actually restrict scanning various folders, but I would imagine that eventually such restrictions would be made such that the void addDiscoveryPath(DiscoveryPath path); entrypoint could restrict or reject additions.
> I believe [~dgolovin] disagrees with this approach. Please discuss.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBDS-4717) Workaround for "Terms and Conditions for CDK have not been signed" doesn't work
by Denis Golovin (Jira)
[ https://issues.jboss.org/browse/JBDS-4717?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-4717.
-------------------------------
Resolution: Won't Fix
Installer was discontinued. Closing.
> Workaround for "Terms and Conditions for CDK have not been signed" doesn't work
> -------------------------------------------------------------------------------
>
> Key: JBDS-4717
> URL: https://issues.jboss.org/browse/JBDS-4717
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.0.0.GA
> Environment: MacOS High Sierra
> Reporter: Andrea Battaglia
> Assignee: Denis Golovin
> Priority: Blocker
>
> The RedHat Development Suite Installer, version 2.3.0-GA-2018-04-19-628, shows the message "Terms and Conditions for CDK have not been signed".
> Following the workaround found in the official installation guide at link [here|https://access.redhat.com/documentation/en-us/red_hat_development_su...], I've downloaded the latest version of the CDK installer (3.5.0-1), but the installer still shows the error.
> And, of course, I've subscribed the Developer Program long time ago connecting the account to my Red Had one.
> I've additionally tried to download the CDK with the same version as the one proposed by the RedHat Development Suite Installer (3.4.0-2), but nothing has changed.
> Even unselecting the CDK in the installer, the error block the installation process.
> Could you please provide support?
> thanks a lot in advance
> Andrea
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBDS-4717) Workaround for "Terms and Conditions for CDK have not been signed" doesn't work
by Denis Golovin (Jira)
[ https://issues.jboss.org/browse/JBDS-4717?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4717:
-----------------------------------
Assignee: Denis Golovin
> Workaround for "Terms and Conditions for CDK have not been signed" doesn't work
> -------------------------------------------------------------------------------
>
> Key: JBDS-4717
> URL: https://issues.jboss.org/browse/JBDS-4717
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.0.0.GA
> Environment: MacOS High Sierra
> Reporter: Andrea Battaglia
> Assignee: Denis Golovin
> Priority: Blocker
>
> The RedHat Development Suite Installer, version 2.3.0-GA-2018-04-19-628, shows the message "Terms and Conditions for CDK have not been signed".
> Following the workaround found in the official installation guide at link [here|https://access.redhat.com/documentation/en-us/red_hat_development_su...], I've downloaded the latest version of the CDK installer (3.5.0-1), but the installer still shows the error.
> And, of course, I've subscribed the Developer Program long time ago connecting the account to my Red Had one.
> I've additionally tried to download the CDK with the same version as the one proposed by the RedHat Development Suite Installer (3.4.0-2), but nothing has changed.
> Even unselecting the CDK in the installer, the error block the installation process.
> Could you please provide support?
> thanks a lot in advance
> Andrea
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JBIDE-26435) Hibernate JPA Model Generator and Java 11
by Cody Lerum (Jira)
[ https://issues.jboss.org/browse/JBIDE-26435?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-26435:
------------------------------------
OK let's close this. It must be some other interaction with my more complicated project and JDT 11
> Hibernate JPA Model Generator and Java 11
> -----------------------------------------
>
> Key: JBIDE-26435
> URL: https://issues.jboss.org/browse/JBIDE-26435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.9.0.Final
> Reporter: Cody Lerum
> Priority: Major
> Attachments: screenshot-1.png
>
>
> Not sure if this ends up being related to Jboss tools or just the Eclipse JDT
> But on 2018-09 with 4.9.Final a project cannot be cleanly built using the org.hibernate:hibernate-jpamodelgen
> Everything builds and then at the end it seems to delete the generated sources.
> This only occurs it the Java 11 support plugin is installed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBDS-4731) Missing datatools.enablement features since 12.0
by Nick Boldt (Jira)
[ https://issues.jboss.org/browse/JBDS-4731?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4731:
-----------------------------
Sprint: devex #156 October 2018
> Missing datatools.enablement features since 12.0
> ------------------------------------------------
>
> Key: JBDS-4731
> URL: https://issues.jboss.org/browse/JBDS-4731
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 12.0.0.GA
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Priority: Major
> Fix For: 12.10.0.AM1
>
> Attachments: 12.9.0.GA.png, 2018-09.png
>
>
> As reported on StackOverflow, it is not possible to create third parties JBDC drivers since 12.0.0.GA. Some org.eclipse.datatools.enablement features are misssing. See the captures for the list
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months