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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBTIS-531:
----------------------------------

Shared 3rd party requirements should be in the shared TP, so that all parts of IS can use the same TP. 

If there's something in one project's needs which CONFLICTS with another project's needs, those projects need to sort that out (eg., depending on incompatible versions of the same IU, which would prevent co-installation).

If you need a way to build the "dummy" plugin outside of the TP so that it can be consumed by the TP, then by Fuse/Teiid/others, I would suggest we move that plugin to the Locus project and build it there along with all the other stuff that the IS requires.

So, then, the process for building in the IS is:

a) find dependency in JBT, Eclipse Orbit, Eclipse Mars/Neon, another Eclipse project, etc. and mirror that onto download.jboss.org/jbosstools/updates/requirements/<upstream-project>/<version>/; or
b) create dependency in JBoss Locus, build it, and publish to JBoss Nexus; then
c) add dependency to IS TP
d) build IS project(s)
e) build IS aggregations


> 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-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)