Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@simonellistonball the main thing with the integration tests, is that due
to the nature of the dependencies between the tests and the parsers, the
integration test topologies, when loading the parsers by name, find them in the
system classloader, as opposed to the bundle loading mechanism. To that end, I
created a new module, with only an integration test and no dependencies that is
sure to load from the bundle class loaders in the test : the bundle extension
test mentioned above.
again, without looking at the code, testing the system with these changes
should be a "everything just works like it did before" operation, with the
exception of metron-docker ( top level ) - which I am not sure how to bring
forward since it does things differently.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
