[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

[John Verhaeg (JIRA)]

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

John Verhaeg commented on JBIDE-6292:
-------------------------------------

Yes :-)  It's available publicly as a simple jar, but we packaged it within an OSGI plug-in so any of our projects can make use of it.  The jar just offers informational concurrency-related tags for marking code as immutable, threadsafe, etc.  It's doesn't affect the application in any way, but it's very useful for ensuring our code adheres to what concurrency policy was initially setup for particular classes.  We'll go after c) first and investigate the license, and if that fails, we'll probably just opt for a).

> 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