Exclude Eclipse Sisu (CDI implementation)

[mariofusco]

…tion processor in org.eclipse.sisu.inject

[gsmet]

@stuartwdouglas any idea why we have this dependency coming and why it generates this file in the Kogito case?

[mariofusco]

@gsmet @stuartwdouglas apparently the annotation processor in that dependency is explicitly made (God knows why) to generate that javax.inject.Named file, see https://www.eclipse.org/sisu/docs/api/org.eclipse.sisu.inject/reference/org/eclipse/sisu/space/SisuIndexAPT6.html

[mariofusco]

@gsmet @stuartwdouglas in reality that jar seems to be explicitly made to be used inside a maven plugin to generate that file, see http://www.eclipse.org/sisu/docs/api/org.eclipse.sisu.mojos/ I think it doesn't make sense to have it among our dependencies

[stuartwdouglas]

I have no idea what this does, I assume it is part of the internals of JUnit 5.

[emmanuelbernard]

I'm a noob but should this exclusion be in our bom instead? Otherwise +1 for the exclusiong. Sisu is a CDI impl so we don't want it in.

[gsmet]

Closing this one in favor of #2986 for a more general fix.

Typically, the Kogito quickstart did generate a file too so we really need to exclude it from the JUnit artifact.