Github user mattf-horton commented on the issue:

    https://github.com/apache/metron/pull/530
  
    I compared with both nifi 1.3.0, which is a couple commits newer than your 
code, and nifi 1.1.2, which is a few commits older than your code.  They are 
different of course, but both are quite different than this PR's code tree:
    ```code
    -------------
    bundles-lib/src/main/java/org/apache/metron/bundles:
    
    BundleClassLoader.java              BundleThreadContextClassLoader.java     
ExtensionMapping.java           annotation
    BundleClassLoaders.java             BundleUnpacker.java                     
InstanceClassLoader.java        bundle
    BundleCloseable.java                ExtensionClassInitializer.java          
NotInitializedException.java    util
    BundleManifestEntry.java    ExtensionManager.java
    
    ./annotation/behavior:
    RequiresInstanceClassLoading.java
    
    ./bundle:
    Bundle.java         BundleCoordinate.java   BundleDetails.java
    
    ./util:
    BundleProperties.java       FileUtilities.java      HDFSFileUtilities.java  
VFSClassloaderUtil.java
    BundleUtil.java             FileUtils.java          StringUtils.java        
VFSFileUtilities.java
    
    -------------
    Ignoring for now the many files at the level of nifi-framework,
    nifi-nar-utils/src/main/java/org/apache/nifi: [rel/1.1.2]
    
    ./nar:
    ExtensionManager.java               NarClassLoader.java     
NarThreadContextClassLoader.java
    ExtensionMapping.java               NarClassLoaders.java    NarUnpacker.java
    InstanceClassLoader.java    NarCloseable.java
    
    ./util:
    FileUtils.java
    
    -------------
    In [rel/1.3.0] this changed to:
    
    ./nar:
    ExtensionMapping.java       NarClassLoader.java     NarManifestEntry.java   
SystemBundle.java
    NarBundleUtil.java  NarClassLoaders.java    NarUnpacker.java
    
    ./util:
    FileUtils.java
    -------------
    which is actually quite a bit different, but same essential structure.
    ```



---
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.
---

Reply via email to