[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/10/15 5:38 AM:
-----------------------------------------------------------------
Created a [PR|https://github.com/jbosstools/jbosstools-locus/pull/51] to address the minor deficiences in the screenshot.
+Update+
Created [LOCUS Jira|https://issues.jboss.org/browse/LOCUS-48]
was (Author: phantomjinx):
Create a [PR|https://github.com/jbosstools/jbosstools-locus/pull/51] to address the minor deficiences in the screenshot.
> 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
> Assignee: Paul Richardson
> Priority: Blocker
> Attachments: TP-issues.png
>
>
> 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] (LOCUS-48) Minor errors in plugin names
by Paul Richardson (JIRA)
Paul Richardson created LOCUS-48:
------------------------------------
Summary: Minor errors in plugin names
Key: LOCUS-48
URL: https://issues.jboss.org/browse/LOCUS-48
Project: JBoss Tools Locus
Issue Type: Bug
Reporter: Paul Richardson
Priority: Minor
Couple of the plugins have incorrect names when viewing them through eclipse.
--
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 commented on JBTIS-531:
---------------------------------------
Create a [PR|https://github.com/jbosstools/jbosstools-locus/pull/51] to address the minor deficiences in the screenshot.
> 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
> Assignee: Paul Richardson
> Priority: Blocker
> Attachments: TP-issues.png
>
>
> 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 Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBTIS-531:
--------------------------------------
{quote}I noticed though that both the stub plugin and one of the saxon plugins in Locus are displaying odd names when the .target file is opened in Eclipse (see attached screengrab). This is not greatly important but wonder if they could be amended prior to Locus 1.4.0 goes Final? {quote}
Please open a Jira again Locus, so at least it's logged, and we'll evaluate whether it's something we can/want to do in 1.4.0.Final.
> 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
> Assignee: Paul Richardson
> Priority: Blocker
> Attachments: TP-issues.png
>
>
> 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 updated JBTIS-531:
----------------------------------
Attachment: TP-issues.png
> 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
> Assignee: Paul Richardson
> Priority: Blocker
> Attachments: TP-issues.png
>
>
> 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 commented on JBTIS-531:
---------------------------------------
Designer is fine with the new TP [PR to be merged|https://github.com/Teiid-Designer/teiid-designer/pull/522].
I noticed though that both the stub plugin and one of the saxon plugins in Locus are displaying odd names when the .target file is opened in Eclipse (see attached screengrab). This is not greatly important but wonder if they could be amended prior to Locus 1.4.0 goes Final?
> 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
> Assignee: Paul Richardson
> Priority: Blocker
>
> 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-21067) Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21067?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21067:
-----------------------------------
Issue Type: Bug (was: Feature Request)
> Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21067
> URL: https://issues.jboss.org/browse/JBIDE-21067
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
>
> When debugging JavaScript with ChromeDevTools for Java it creates special project inside current workspace and populate it with .js files using eclipse file system (EFS) API. IReource instance for .js file inside project returns null if requested for location through IResource.getLocation() method. null is valid return value according to JavaDoc for the method.
> Now JBossTools code fails with NullPointerException and pollutes Error Log View
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:368)
> at org.jboss.tools.jst.web.ui.navigator.XContentProvider.hasChildren(XContentProvider.java:96)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.hasChildren(SafeDelegateTreeContentProvider.java:112)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.callNormalHasChildren(NavigatorContentServiceContentProvider.java:444)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.access$4(NavigatorContentServiceContentProvider.java:439)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$3.run(NavigatorContentServiceContentProvider.java:407)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:392)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:436)
> at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2124)
> at org.eclipse.jface.viewers.TreeViewer.isExpandable(TreeViewer.java:538)
> at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2162)
> at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2844)
> at org.eclipse.jface.viewers.TreeViewer.updatePlus(TreeViewer.java:786)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:840)
> at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:816)
> at org.eclipse.jface.viewers.AbstractTreeViewer$$Lambda$43/10378869.run(Unknown Source)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1489)
> at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21067) Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21067?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-21067:
---------------------------------------
[~akazakov] we might need to fix it in 4.3.x stream as well
> Error Log view is polluted with NullPointerExceptions when debugging JavaScript with ChromeDevTools
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21067
> URL: https://issues.jboss.org/browse/JBIDE-21067
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
>
> When debugging JavaScript with ChromeDevTools for Java it creates special project inside current workspace and populate it with .js files using eclipse file system (EFS) API. IReource instance for .js file inside project returns null if requested for location through IResource.getLocation() method. null is valid return value according to JavaDoc for the method.
> Now JBossTools code fails with NullPointerException and pollutes Error Log View
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:368)
> at org.jboss.tools.jst.web.ui.navigator.XContentProvider.hasChildren(XContentProvider.java:96)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.hasChildren(SafeDelegateTreeContentProvider.java:112)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.callNormalHasChildren(NavigatorContentServiceContentProvider.java:444)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.access$4(NavigatorContentServiceContentProvider.java:439)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$3.run(NavigatorContentServiceContentProvider.java:407)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:392)
> at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.hasChildren(NavigatorContentServiceContentProvider.java:436)
> at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2124)
> at org.eclipse.jface.viewers.TreeViewer.isExpandable(TreeViewer.java:538)
> at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable(AbstractTreeViewer.java:2162)
> at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:2844)
> at org.eclipse.jface.viewers.TreeViewer.updatePlus(TreeViewer.java:786)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:840)
> at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:816)
> at org.eclipse.jface.viewers.AbstractTreeViewer$$Lambda$43/10378869.run(Unknown Source)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1489)
> at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882){code}
--
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 commented on JBTIS-531:
----------------------------------
Thanks [~mickael_istria] for the quick Locus build. I've encorporated the BC stub jar from the 1.4.0-SNAPSHOT Locus build into a SNAPSHOT build of the Luna JBTIS TP. [~lhein] / [~blafond] [~phantomjinx] - please modify your JBTIS TP to 4.2.9-SNAPSHOT . [~phantomjinx] should pull the BC stub from Teiid Des. Also - [~lhein] - please build your Fuse Tooling TP. I built it and it is okay but we should see that you're okay as well.
ref: https://origin-repository.jboss.org/nexus/content/repositories/snapshots/...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.9-SN...
When all's well I'll build a .Final stable TP.
Thkx!
> 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
> Assignee: Paul Richardson
> Priority: Blocker
>
> 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