Github user mattf-horton commented on a diff in the pull request:
    --- Diff: bundles-lib/ ---
    @@ -0,0 +1,79 @@
    +# Apache Metron Bundles
    +Apache Metron Bundles and this documentation are a derivitave of the 
[Apache Nifi]( 
    +When software from many different organizations is all hosted within
    +the same environment, Java ClassLoaders quickly
    +become a concern. If multiple components have a dependency on the same
    +library but each depends on a different
    +version, many problems arise, typically resulting in unexpected
    +behavior or `NoClassDefFoundError` errors occurring.
    +In order to prevent these issues from becoming problematic, Apache NiFi
    +introduces the notion of a NiFi Archive, or NAR.  The Apache Metron 
project has adapted and extended the NAR system as
    +Apache Metron Bundles.
    +A BUNDLE allows several components and their dependencies to be packaged
    +together into a single package.
    +The BUNDLE package is then provided ClassLoader isolation from other 
    +packages. Developers should always deploy their Apache Metron Extensions 
as BUNDLE packages.
    +To achieve this, a developer creates a new Maven Artifact, which we
    +refer to as the BUNDLE artifact. The packaging is
    +set to `bundle`. The `dependencies` section of the POM is then created so
    +that the BUNDLE has a dependency on all Extension Components that are to 
be included within the BUNDLE.
    +In order to use a packaging of `bundle`, we must use the 
`bundles-maven-plugin` module.
    +This is included by adding the following snippet to the bundle's pom.xml:
    +    <plugins>
    +        <plugin>
    +            <groupId>org.apache.metron</groupId>
    +            <artifactId>bundles-maven-plugin</artifactId>
    +            <version>0.4.0</version>
    --- End diff --
    0.4.1 is the minimum version that actually has bundles-maven-plugin.

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 or file a JIRA ticket
with INFRA.

Reply via email to