[jbosstools-issues] [JBoss JIRA] (JBTIS-531) Bouncy Castle causes Fuse Tooling full source TP build failure.

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126103#comment-13126103 ] 

Mickael Istria commented on JBTIS-531:
--------------------------------------

[~blafond] thanks.
[~phantomjinx] told me a bit about it earlies today, and I have a suggestion to make, since it seems to be mainly an issue of whether it's possible for a 3rd party to consume/bind to bouncycastle from Teeid Designer: in Apache DS, what about nesting the jar inside the plugin (jar) that needs it and not exporting its classes? Or, in Teeid Designer, create a plugin that "nests" bouncycastle and only reexports the few necessary legal-friendly classes. In that way, it's possible to "hide" part or globality of bouncycastle to consumers of Teiid Designer, maybe making the legal issue "closed enough" without having to duplicate classes or other ugly hack.
I believe the approach I describe above are matching legal constraints and are better engineering.

> 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-stack/teiiddesigner/9.0.4.Final/plugins/org.teiid.designer.bc.dummy_9.0.4.Final-v20151016-1346-B1206.jar
> 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)