[ https://issues.jboss.org/browse/TEIIDDES-2667?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on TEIIDDES-2667: ----------------------------------------------- First reaction: Yes, this is bad - we can't just include it blindly. Second reaction: since when was this dependency introduced? where in the IS TP do we have this dependency ? I don't recall a TP update review where we added stuff like bouncycastle ? Is there no way that this bouncycastle can be avoided ? We can included/use bouncycastle if it comes without certain of the crypto limiting code - I think Apache has the same limitations here too so one can hope it is okey. We'll need to ping legal on that. About forking - we can't really fork plugins in traditional sense - that would make us conflict in the eclipse ecosystem. We'll have to look into rename the feature bundles or some other way to not overlap. -- This message was sent by Atlassian JIRA (v6.4.11#64026)