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

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12531044#action_12531044 ] 

Nick Boldt commented on JBIDE-6292:
-----------------------------------

I have temporarily added the jcip.annotations plugin to both teiid features. This solves the p2 installation problem, but does not address the licensing issue. 

As such, you may still want to go with option (c) - create a new feature to house this plugin and make it available on the update site.

Let me know when you've created the new feature, and I can assist in wiring up the update site if needed (just add the new feature ID to the site/site.xml file). You'll also want to make sure the new feature is added to the features/pom.xml and that there's a pom.xml in the root of the new feature itself.



> 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: Barry LaFond
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira