Github user sesuncedu commented on the issue:
https://github.com/apache/maven-indexer/pull/13
@cstamas Squashbasing gives the cleanest trees. Just make sure to give
yourself credit for the commits of yours that were cherry-picked.
index-reader should be identical for both branches. There's only a single
package, and I bumped the OSGI package version to 5.2.0, since the additional
public static fields are a minor API change over 5.1.2 . Since nexus is using
karaf features / pax-aether-url , this isn't as necessary or helpful or as it
might be, but it does mean that the feature assembly can safely refer to the
6.0 index-reader snapshot, since the osgi package version is explicitly
backwards compatible.
I actually ended up doing a third version of the changes as kludges on top
of the nexus-public maven repository plugin. The main annoyance with
index-reader was having to subclass Expander / Compactor to handle the
additional fields, where a default mapping would have been simple.
Since I needed to build some mapping tables anyway to stash the relevant
manifest headers in an asset child map where they wouldn't get in the way,
doing Expander/Compactor wasn't that much of an extra hassle, but if the
index-reader is used to build federations, it is useful to be able to have
unrecognized fields be passed through as strings (e.g. if jigsaw is released,
exchanging headers from module-info.class (and now possibly the manifest?) will
be useful for federated systems).
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
