Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@mmiklavc
1. I don't think we want to, or have to track it as upstream. But we do
want to keep track of bug fixes and improvements to areas where we have not
deviated. That is my current thinking.
2. I certainly did look at
[#468](https://github.com/apache/metron/pull/468). Here is how we are related:
- 777 uses the same VFS Classloader, although I have modified a new version
of the classloader to load a bundle as a compound filesystem. That is to say,
instead of VFSClassloader loading a number of Jar uris, it loads a bundle, and
then finds all the embedded dependency jars as well. This I believe is an
improvement on the NAR system, since there is no longer a requirement to
unbundle the NAR into a working directory and all the overhead that has.
- 777 uses the ClassIndex System. I have replaced the NAR service loader
dependency ( in the archetype ) with ClassIndex. I have also made the loaders
work with class index's multiple ways for marking classes. This is an
improvement on the NAR system because:
1. You do not have to manually maintain the service file in the jar metadata
2. It is faster
One of my goals is to have Extensions/Bundles+archetypes for Stellar
libraries as well. I believe that 777 is done in a way that is comparable with
that goal, and enables it.
---
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.
---
