Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/530
Maybe I am misunderstanding the functionality here, but I see a split
looking like this. Of course, you know the work better than me, so maybe there
is a slightly different way we need to tackle this.
(1) PR 1: Introduce bundle/extension mechanism. We would have
unit/integration tests for this functionality. Your manual test steps would
describe step-by-step how to create a parser extension (meaning all the steps
that your Maven plugin automates).
(2) PR 2: Introduce the Maven plugin. You would have unit tests for the
plugin along with a manual test plan describing how a user would go about using
the plugin to create a parser extension.
(3) PR 3: Migrate the parsers to use the bundle/extension mechanism. You
would again have unit/integration tests. Your manual test steps would describe
how to build and deploy the parsers using your extension mechanism.
(4) PR 4: Updates to the Ambari MPack. This just automates some of the
setup steps that were performed manually in the previous PRs.
---
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.
---
