[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:
--------------------------------------
Since it seems like it's not a sustainable solution, I believe it would be better to keep the bouncycastle "dummy" bundle in Teeid, rather than sharing it with the world on Locus.
However, now that I've learned it's a complex legal issue and it's urgent, feel free to proceed to what's best to fix it in good time, even if it implies adding "volatile" content to Locus.
> 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-21057) Web Services Tester locks up when editing
by Brian Fitzpatrick (JIRA)
Brian Fitzpatrick created JBIDE-21057:
-----------------------------------------
Summary: Web Services Tester locks up when editing
Key: JBIDE-21057
URL: https://issues.jboss.org/browse/JBIDE-21057
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.3.Final
Environment: Mac setup:
• OS X 10.9.4
• JBDS 8.1.0.GA-v20150327-1349-B467
• Fuse Tooling 7.2.3.v20151008-1250-H108-CR2
• Switchyard 2.0.1v20150923-1505-H19-CR1
• JRE 1.7.0_25-b15
Reporter: Brian Fitzpatrick
Priority: Critical
Attachments: OSX_WebServicTesterHang.rtf
When using the tree view in the Web Service Tester to edit request message values, the entire workbench freezes. Nothing appears in the error log and I have been unable to reproduce in a Windows environment.
Will get a simpler reproducible case, but am posting what [~jmurphey] has documented so far.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21057) Web Services Tester locks up when editing
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21057?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick reassigned JBIDE-21057:
-----------------------------------------
Assignee: Brian Fitzpatrick
> Web Services Tester locks up when editing
> ------------------------------------------
>
> Key: JBIDE-21057
> URL: https://issues.jboss.org/browse/JBIDE-21057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.3.Final
> Environment: Mac setup:
> • OS X 10.9.4
> • JBDS 8.1.0.GA-v20150327-1349-B467
> • Fuse Tooling 7.2.3.v20151008-1250-H108-CR2
> • Switchyard 2.0.1v20150923-1505-H19-CR1
> • JRE 1.7.0_25-b15
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Priority: Critical
> Attachments: OSX_WebServicTesterHang.rtf
>
>
> When using the tree view in the Web Service Tester to edit request message values, the entire workbench freezes. Nothing appears in the error log and I have been unable to reproduce in a Windows environment.
> Will get a simpler reproducible case, but am posting what [~jmurphey] has documented so far.
--
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:
----------------------------------
[~mickael_istria] [~phantomjinx] [~blafond] [~nickboldt] [~maxandersen] [~ganandan-Redhat] [~lhein]
Regarding Mickael's comment above - Paul R - is this suggestion something that you could do in Teiid Designer? The fact that Eclipse legal is okay with it in Eclipse orbit doesn't mean Red Hat legal agrees. There is some urgency to this as we need it for our Luna release (now in CR test cycle) as well as Mars. There's also the issue with the bouncy castle challenge window on install that we can not have. Mickael - would it make sense to go with the Paul R Locus PR as it exists now and revisit it post-Luna? We need to reach consensus on how this should be addressed.
Thkx all.
> 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-21056) Predefined labels are not treated in same way
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21056:
-------------------------------------
Summary: Predefined labels are not treated in same way
Key: JBIDE-21056
URL: https://issues.jboss.org/browse/JBIDE-21056
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Environment: Nightly JBT. OpenShift tooling build Version: 3.1.0.Beta1-v20151104-0336-B66
Reporter: Marián Labuda
Labels in a New OpenShift Application wizard on the page containing label managing are not treated equally. When application is build on a template with more predefined labels, the first one listed in the table with labels is read-only, but the second one (maybe also further labels) are editable and removable. We should treat all labels equally. Either take them as read only from templates or allow user to modify them. As an testing example was used template located at https://github.com/jboss-openshift/application-templates/blob/master/eap/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21056) Predefined labels are not treated in same way
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21056?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21056:
----------------------------------
Labels: application_wizard openshift_v3 (was: )
> Predefined labels are not treated in same way
> ---------------------------------------------
>
> Key: JBIDE-21056
> URL: https://issues.jboss.org/browse/JBIDE-21056
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Environment: Nightly JBT. OpenShift tooling build Version: 3.1.0.Beta1-v20151104-0336-B66
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
>
> Labels in a New OpenShift Application wizard on the page containing label managing are not treated equally. When application is build on a template with more predefined labels, the first one listed in the table with labels is read-only, but the second one (maybe also further labels) are editable and removable. We should treat all labels equally. Either take them as read only from templates or allow user to modify them. As an testing example was used template located at https://github.com/jboss-openshift/application-templates/blob/master/eap/...
--
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 Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-531?page=com.atlassian.jira.plugin.... ]
Lars Heinemann commented on JBTIS-531:
--------------------------------------
In that case it makes more sense to use the orbit one.
> 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] (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:
----------------------------------
Capturing this email from Roland Grunberg:
The bouncycastle.bcprov has been approved by Eclipse Legal for distribution through Orbit, under the condition that certain classes be excluded.
I can't really answer the legal question but some quick searching shows that it's either approved [1] or not subject to those export controls [2].
[1] http://www.bouncycastle.org/wiki/display/JA1/Frequently+Asked+Questions#F...
[2] https://en.wikipedia.org/wiki/Bouncy_Castle_%28cryptography%29
> 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] (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:
--------------------------------------
[~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-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