Quick question:

I noticed a bug on the path used by binding-sca-runtime when doing a
cross-classloader (e.g. cross-Contribution) copy.

Not sure how important it is to people to keep the tests structured
relatively simply...

I'm thinking I'll add the test to the binding-sca-runtime module and
just check-in a couple contribution JARs as source, since that's
easier to me than trying to build/copy/package things in two JARs.
(I see some modules e.g. 'contribution' checking in JARs as source).

Kind of ugly not to have the Java as source though...

Does anyone have a better suggestion on where to add a test for this case?

Thanks,
Scott

Reply via email to