Bug 424711 - Provide infrastructure to discover 3rd party contributions
Summary: Provide infrastructure to discover 3rd party contributions
Status: NEW
Alias: None
Product: Xtend
Classification: Tools
Component: Backlog (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-28 05:24 EST by Joerg Reichert CLA
Modified: 2014-11-11 09:01 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Reichert CLA 2013-12-28 05:24:54 EST 
Analogous to Mylyn Task Repository Connectors (help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.mylyn.help.ui%2FMylyn%2FUser_Guide%2FTask-Repository-Connectors.html) and M2E connectors (http://objectledge.org/confluence/display/TOOLS/M2E+Connectors) there should be discovery mechanim in place to find Active Annotations and Generator Fragment provided by third parties.

There are already existing annotation libraries like:
 * https://github.com/oehme/xtend-contrib
 * https://bitbucket.org/msigmond/concurrent-annotations/
 * https://github.com/gzsombor/ixlibs
 * and some more: https://github.com/search?l=Xtend&o=desc&q=TransformationContext&ref=advsearch&s=indexed&type=Code
Comment 1 Jan Koehnlein CLA 2014-11-11 08:52:45 EST 
Maybe a list of projects with AAs in the community section of the Xtend homepage would suffice for the moment. 

AAs empower the user to extract their own abstractions in their own way, so personally I don't like to think about them as reusable 3rd party libraries. Even for the very simple AAs like @Accessors we found a lot of border cases, showing that it is hard to build them bullet proof for all usecases. So the existing AAs could serve as examples how to build your own ones rather than as consumable libs.