[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6292) Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations

Teiid Designer Update site does not include third party requirements like http://mvnrepository.com/artifact/net.jcip/jcip-annotations ------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-6292 URL: https://jira.jboss.org/browse/JBIDE-6292 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng Reporter: Nick Boldt Assignee: John Verhaeg Priority: Critical Fix For: 3.2.0.M1 Various solutions are possible... a) don't use them b) find an update site where that's published and tell p2 (via metadata) how to find that associate site (like JBT does for m2eclipse, birt2.5, etc.) c) create a new "third party stuff" feature (or add this/these plugins to an existing feature) so that the generated site will include them; as such you'll be **REDISTRIBUTING** them, so be aware of license limitations with doing so ---- if (a)... my work is done. if (b)... well, the burden of license acceptance is on someone else and not on us... but I still need to write some code to make the site aggregate the new metadata. Prolly require Buckminster aggregator if (c), you need to ensure that the license text in that feature is VERY CLEAR about which license(s) must be accepted when installing the feature (since they won't all be EPL, I'm guessing) --- Frankly, from a simplicity POV, I prefer (c), but ONLY if the license(s) are compatible and you and PM are cool with that. Second choice would be (b), as it's more work for me. This only works if there's a site available (or we create one). Failing that, I like (a), but that's more work for the Teiid devs -- requiring them to implement using a different library.