[ https://issues.apache.org/jira/browse/MINDEXER-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931824#comment-15931824 ]
ASF GitHub Bot commented on MINDEXER-97: ---------------------------------------- Github user sesuncedu commented on the issue: https://github.com/apache/maven-indexer/pull/13 I have been consistently confused about which branch is live, so it would not surprise me either way ☺️. I had been working against main on some code to use the central index to build a database for use as an OSGI resolver. I noted the missing fields... after I'd done a whole bunch of defactoring to decouple index reading from the rest of the code.... D'oh! I can cross port these changes to master (well, not the index reader ones) :) My main goal is to get the extra fields into the index on central. I'd presume that 5.1.2 would be the smaller jump. Would it be possible to make a 5.1.2 release? And would it be possible to have run it running on central in the near future? My primary concern if I were the admin would be the need to perform the sequential read of the entire bundle jar to generate the sha-256 checksum. It ought not be too significant a burden compared to the overall level of activity, but depending on what else is going on on the storage side, it might be annoying. I haven't checked to see how full reindexing is handled, and if a previously calculated SHA-256 could be fetched for less than the cost of the sequential read (lucene + cache + storage load / architecture = magic). Alternative would be to save SHA-256 hashes in a simple k/v store. (now that full sha-1 has been broken, it is probably time to switch over to SHA-256, but that's a much more pervasive change). > Add OSGi 5.0 MANIFEST headers to OsgiArtifactIndexCreator > --------------------------------------------------------- > > Key: MINDEXER-97 > URL: https://issues.apache.org/jira/browse/MINDEXER-97 > Project: Maven Indexer > Issue Type: Improvement > Reporter: Balazs Zsoldos > > It would be extremely useful if the following MANIFEST headers were added to > the index: > - Require-Capability > - Provide-Capability > - DynamicImport-Package > Especially the first two would be necessary to be able to build up a database > that helps finding dependencies for unsatisfied bundles. -- This message was sent by Atlassian JIRA (v6.3.15#6346)