If choosing from A) and B) I would go for B) and add a dependency (hard one or or greedy optional?) to the Usage.

On 02/15/2016 06:47 PM, Max Rydahl Andersen wrote:

Hey,

I'm working on the inclusion of Aeri into JBoss Tools.

Initial PR is at https://github.com/jbosstools/jbosstools-base/pull/483

I would like to include this into JBoss Tools 4.3 CR1 (the one using Mars.2).

I see two options:

A) add separate plugin (that is what separate PR does now) and users will have
to manually add it, unless we add it to every overall feature like we have done for usage.

B) add this extension point + dependency on aeri plugin into our usage plugin.

With B we get the biggest exposure by far - but we will add a base dependency to Aeri for every plugin we have.

Suggestions welcome on how we can make Aeri available to most people with the smallest impact :)

/max
http://about.me/maxandersen

_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev

_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev