[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Paul Richardson commented on JBTIS-531:
---------------------------------------
Hey [~pleacu]
While I agree that Fuse should not have to add Designer plugins to the dev environment, I disagree with the sentiment of taking Apache directory out of the IS-TP just because only Designer currently pick it up. After all, there are plenty of plugins in the IS-TP that Designer has no need. I feel that a better solution and probably the expectation of the IS-TP is that it is 'complete' and fully compileable on its own. Therefore the designer dummy plugin should be pushed down into the IS-TP.
WDYT?
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
> Priority: Major
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Paul Richardson edited comment on JBTIS-531 at 11/4/15 4:51 AM:
----------------------------------------------------------------
Hey [~pleacu]
While I agree that Fuse should not have to add Designer plugins to the dev environment, I disagree with the sentiment of taking Apache directory out of the IS-TP just because only Designer currently picks it up. After all, there are plenty of plugins in the IS-TP that Designer has no need. I feel that a better solution and probably the expectation of the IS-TP is that it is 'complete' and fully compileable on its own. Therefore the designer dummy plugin should be pushed down into the IS-TP.
WDYT?
was (Author: phantomjinx):
Hey [~pleacu]
While I agree that Fuse should not have to add Designer plugins to the dev environment, I disagree with the sentiment of taking Apache directory out of the IS-TP just because only Designer currently pick it up. After all, there are plenty of plugins in the IS-TP that Designer has no need. I feel that a better solution and probably the expectation of the IS-TP is that it is 'complete' and fully compileable on its own. Therefore the designer dummy plugin should be pushed down into the IS-TP.
WDYT?
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
> Priority: Major
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20740) Change of JVM Monitor "Period to Search JVMs on local host" takes effect only after eclipse restart
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20740?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20740:
-------------------------------------
Well... that was surprisingly challenging to debug ;)
It seems it was SUPPOSED to be storing these values in another plugins' preference store (intentionally), but was storing it in its own plugin's preference store. Both plugins' activators were simply named "Activator", and I'd imagine that when some logging was added to the UI, the new import broke the existing code by storing the values in the UI plugin's preferences rather than the "tools" plugin's.
Another reason to never name your activator "Activator" ;)
As for why it still magically worked on workspace restart, I have absolutely no idea :D I do remember there had previously had the core prefs stored in teh UI plugin, causing a circular dependency, and I had fixed that. But this still worked after that point. I really think the addition of an import is what broke it.
> Change of JVM Monitor "Period to Search JVMs on local host" takes effect only after eclipse restart
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20740
> URL: https://issues.jboss.org/browse/JBIDE-20740
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.0.CR1
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.3.x, 4.4.0.Alpha1
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21050) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21050?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21050:
-------------------------------------
I've submitted a PR, but:
I would like to stress that this is not very well tested since I don't fully understand the usecase of what kind of files create this artifact. I strongly suggest the webservices tool team give this a thorough check and make sure it works before committing it.
> webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-21050
> URL: https://issues.jboss.org/browse/JBIDE-21050
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Rob Stryker
>
> WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules.
> The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later.
> The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb.
> See also: https://issues.jboss.org/browse/JBIDE-20802
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21050) webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-21050:
-----------------------------------
Summary: webservices artifacts should extend ModuleArtifactDelegate to be used by launchbar
Key: JBIDE-21050
URL: https://issues.jboss.org/browse/JBIDE-21050
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Reporter: Rob Stryker
WTP will customize the 'run on server' action to use launch configurations rather than their standard API if the module artifact in question extends ModuleArtifactDelegate instead of implements IModuleArtifact. Launchbar works entirely on launch configurations, and so can only really allow quick access to the run-on-server actions for such modules.
The ModuleArtifactDelegate class provides two methods that you will need to override to give it enough information to properly locate the artifact: serialize and deserialize. The idea is to serialize with enough information such that the artifact can be re-instantiated and unserialized later.
The only class using the getEndpoint() method in JaxrsEndpointModuleArtifact is WSTesterClientDelegate, and this class only gets the endpoint so that it can calculate the endpoint URI and get the HTTP method.... so you'd probably want to move the computeEndpointURI logic into the JaxrsEndpointModuleArtifact, and, on serialization, save the endpoint URI and the http verb.
See also: https://issues.jboss.org/browse/JBIDE-20802
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20802) jax-rs refresh triggers error in server.launchbar on kitchensink example with launchbar wtp installed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20802?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20802:
-------------------------------------
I've attached a PR which both investigates the module artifact in more detail, as well as does nothing at all if the launchbar is disabled. This should fix both concerns.
> jax-rs refresh triggers error in server.launchbar on kitchensink example with launchbar wtp installed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20802
> URL: https://issues.jboss.org/browse/JBIDE-20802
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
>
> Have jboss launchbar tooling installed and then :
> use the kitchensink example (JAvaEE project).
> project shows up with blank/empty JAX-RS Web services node
> Right click and refresh the resources
> I then browse the tree and in logs I get:
> {code}
> java.lang.ClassCastException: org.jboss.tools.ws.jaxrs.ui.internal.launcher.JaxrsEndpointModuleArtifact cannot be cast to org.eclipse.wst.server.core.model.ModuleArtifactDelegate
> at org.jboss.tools.wtp.server.launchbar.objects.ModuleArtifactWrapper.getName(ModuleArtifactWrapper.java:36)
> at org.jboss.tools.wtp.server.launchbar.descriptors.ModuleArtifactLaunchDescriptor.getName(ModuleArtifactLaunchDescriptor.java:45)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.getDescriptorId(LaunchBarManager.java:293)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.addDescriptor(LaunchBarManager.java:301)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.launchObjectAdded(LaunchBarManager.java:342)
> at org.jboss.tools.wtp.server.launchbar.ModuleObjectProvider.selectionChanged(ModuleObjectProvider.java:331)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:237)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.handlePostSelectionChanged(SelectionService.java:122)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$1(SelectionService.java:112)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService$3.selectionChanged(SelectionService.java:80)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:167)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:164)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:161)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:273)
> at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:270)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:114)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356)
> at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:36)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$3.selectionChanged(CompatibilityPart.java:132)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:877)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:874)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1243)
> at org.eclipse.ui.navigator.CommonViewer.handlePostSelect(CommonViewer.java:455)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1269)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
> then when I start clicking around and try working I get error dialogs popping up.
> Looks like it tries to convert things it should not try converting.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20802) jax-rs refresh triggers error in server.launchbar on kitchensink example with launchbar wtp installed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20802?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20802:
-------------------------------------
After some investigation, it seems WTP doesn't use launch configs for these legacy module artifacts that only implement the interface and don't extend the ModuleArtifactDelegate superclass. I've now moved to exclude these types of artifacts from the launchbar.
> jax-rs refresh triggers error in server.launchbar on kitchensink example with launchbar wtp installed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20802
> URL: https://issues.jboss.org/browse/JBIDE-20802
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
>
> Have jboss launchbar tooling installed and then :
> use the kitchensink example (JAvaEE project).
> project shows up with blank/empty JAX-RS Web services node
> Right click and refresh the resources
> I then browse the tree and in logs I get:
> {code}
> java.lang.ClassCastException: org.jboss.tools.ws.jaxrs.ui.internal.launcher.JaxrsEndpointModuleArtifact cannot be cast to org.eclipse.wst.server.core.model.ModuleArtifactDelegate
> at org.jboss.tools.wtp.server.launchbar.objects.ModuleArtifactWrapper.getName(ModuleArtifactWrapper.java:36)
> at org.jboss.tools.wtp.server.launchbar.descriptors.ModuleArtifactLaunchDescriptor.getName(ModuleArtifactLaunchDescriptor.java:45)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.getDescriptorId(LaunchBarManager.java:293)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.addDescriptor(LaunchBarManager.java:301)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.launchObjectAdded(LaunchBarManager.java:342)
> at org.jboss.tools.wtp.server.launchbar.ModuleObjectProvider.selectionChanged(ModuleObjectProvider.java:331)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(SelectionService.java:237)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.handlePostSelectionChanged(SelectionService.java:122)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService.access$1(SelectionService.java:112)
> at org.eclipse.ui.internal.e4.compatibility.SelectionService$3.selectionChanged(SelectionService.java:80)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$4.run(SelectionAggregator.java:167)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyPostListeners(SelectionAggregator.java:164)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$8(SelectionAggregator.java:161)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8$1.run(SelectionAggregator.java:273)
> at org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(RunAndTrack.java:56)
> at org.eclipse.e4.ui.internal.workbench.SelectionAggregator$8.changed(SelectionAggregator.java:270)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:114)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356)
> at org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setPostSelection(SelectionServiceImpl.java:36)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$3.selectionChanged(CompatibilityPart.java:132)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:877)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:874)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1243)
> at org.eclipse.ui.navigator.CommonViewer.handlePostSelect(CommonViewer.java:455)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1269)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
> then when I start clicking around and try working I get error dialogs popping up.
> Looks like it tries to convert things it should not try converting.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-531:
-----------------------------
Summary: Bouncy Castle causes Fuse Tooling full source TP build failure. (was: Bouncy Castle causes full source TP build failure.)
> Bouncy Castle causes Fuse Tooling full source TP build failure.
> ---------------------------------------------------------------
>
> Key: JBTIS-531
> URL: https://issues.jboss.org/browse/JBTIS-531
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 9.0.0.Alpha2, 8.0.4.CR2
> Reporter: Paul Leacu
>
> Here is the issue. The JBTIS TP has a reliance on bouncycastle that was introduced as an indirect dependency by Teiid Designer because they needed the Apache directory features including the org.apache.directory.studio.connection.ui feature. The bcprov feature was removed from the JBTIS TP and Teiid Designer added a dummy feature to satisfy maven. This was built and everything in the IS builds and installs fine - no one directly needed bouncycastle.
> Fuse Tooling builds a local development-only full source target platform based on the JBTIS TP. This causes all dependencies to be fully resolved which causes them to fail their target platform development-only build:
> {code}
> mvn -Pmultiple2repo -U -Dmirror-target-to-repo.includeSources=true clean install
> ...
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.x509.extension 0.0.0' but it could not be found
> {code}
> you may also see this error:
> {code}
> [ERROR] Software being installed: org.apache.directory.studio.connection.ui 2.0.0.v20150618
> [ERROR] Missing requirement: org.apache.directory.studio.connection.ui 2.0.0.v20150618 requires 'package org.bouncycastle.asn1 0.0.0' but it could not be found
> {code}
> Both of these plugins can be found (in stub form) here:
> http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...
> How should this be fixed? Both Teiid Designer and Fuse Tooling use the JBTIS TP. Fuse needs this development TP to debug Fuse and SAP issues. They shouldn't have to incur a dependency that has nothing to do with them. If we pull the entire Apache directory dependency block out of the IS TP then Teiid Des will have to go back to creating their own merged TP.
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months