Re: [capra-dev] Notification system in artifact handler breaks support f

[Jens Lideström <jens.lidestrom@xxxxxxxxxxx>]

> The generic models can be avoided by not installing the org.eclipse.capra.generic.feature

Yes, that has been our strategy so far. But this doesn't work any more since now the important artifact handlers can't be installed without the generic model.

The motivation for my quick fix solution thoughts in the previous mail was this:

Maybe we can find a way to have Capra choose the ReqTool model in case both the generic model and the ReqTool model are installed. Maybe that is easier and quicker that to get rid of all uses of the generic model in all the artifact handlers.

/Jens

2017-06-29 14:16 GMT+02:00 Hans-Erik Floryd <hans-erik.floryd@xxxxxxxxxxx>:

On 29 June 2017 at 13:57, Jens Lideström <jens.lidestrom@xxxxxxxxxxx> wrote:
> But we would still need a way to specify that we want the ReqTool model to
> be used, even if the generic model is present. Right now its a matter of
> chance I think. Sometimes it works because the ReqTool model happens to be
> first in the list of extension point contributions; sometimes it doesn't
> work.

The generic models can be avoided by not installing the
org.eclipse.capra.generic.feature feature. If the user installs
reqtool it should be possible to avoid pulling in that feature. Of
course if the user installs that feature explicitly then things will
break.

/Hans-Erik

_______________________________________________
capra-dev mailing list
capra-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/capra-dev