On 16 Feb 2016, at 1:04, Alexey Kazakov wrote:
If choosing from A) and B) I would go for B) and add a dependency
(hard one or or greedy optional?) to the Usage.
Just realised we didn't conclude this on the mailing list.
For now the only way to handle this I went with enabling it in the usage
plugin so it is enabled globally for anything that already has usage.
It has one caveat though and that is we can't separate the error
tracking for devstudio and jboss tools but
we'll have to live with that for now until there is a mechanism in Aeri
to provide an override.
On 02/15/2016 06:47 PM, Max Rydahl Andersen wrote:
> I'm working on the inclusion of Aeri into JBoss Tools.
> Initial PR is at
> I would like to include this into JBoss Tools 4.3 CR1 (the one using
> 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 :)
> jbosstools-dev mailing list
jbosstools-dev mailing list