[MINDEXER-81] Make ArtifactInfo extensible #539

Activity

1. jira-importer commented on Aug 19, 2014

   

   jira-importer

   on Aug 19, 2014

   Author

   More actions

   Martin Todorov commented

   @Tamas: Could you please elaborate a bit further?
2. jira-importer commented on Aug 27, 2014

   

   jira-importer

   on Aug 27, 2014

   Author

   More actions

   Tamas Cservenak commented

   In short, AI should be a "map", not have fixed fields like now. Hence, user adding new IndexCreator is easily able to introduce new fields to index (that's possible even now), and also get them back via standard API.

   Look at this class
   https://github.com/apache/maven-indexer/blob/master/indexer-core/src/main/java/org/apache/maven/index/ArtifactInfoRecord.java
3. jira-importer commented on Mar 30, 2017

   

   jira-importer

   on Mar 30, 2017

   Author

   More actions

   Laird Nelson commented

   I have a concrete use case that I'll elaborate here. I am a new user of Lucene (no idea what I'm doing :-)) and of the Maven Indexer. Hopefully my explanation below will give you insight into how a person new to this project approaches it.

   I'd like to write an IndexCreator that, in the abstract, adds fields to the index that represent certain contents of META-INF/MANIFEST.MF files. I'd like to let users search, for example, for artifacts containing META-INF/MANIFEST.MF files with Fred in their Class-Path headers.

   I see no way to simply write an IndexCreator (and no other code) to do this. It seems that I would (with the current architecture) have to edit ArtifactInfo to have some new instance variables to store this information.

   It also looks like other IndexCreator implementations that work with META-INF/MANIFEST.MF files, like the OsgiArtifactIndexCreator, do exactly this: I note that ArtifactInfo, though it would seem to want to be a generic sort of class, has fields in it like bundleSymbolicName, suggesting that for every indexer an edit to ArtifactInfo's source code is necessary. This shouldn't be the case.
4. jira-importer commented on Nov 24, 2017

   

   jira-importer

   on Nov 24, 2017

   Author

   More actions

   Tamas Cservenak commented

   Completely agreed and the comment above is in agreement with foreseen change. Still, am moving this change out of 6.0 release, as it would introduce breaking change (ArtifactInfo would need to be rewritten), will be done post 6.0
5. jira-importer commented on Nov 4, 2022

   

   jira-importer

   on Nov 4, 2022

   Author

   More actions

   Tamas Cservenak commented

   Move out from 7.0.0, this is not trivial effort, but release is imminent.
6. jira-importer

   added

   enhancementNew feature or requestNew feature or request

   priority:majorMajor loss of functionMajor loss of function

   on Jun 12, 2025
7. slachiewicz

   added

   breakingPull requests that break existing featuresPull requests that break existing features

   and removed

   priority:majorMajor loss of functionMajor loss of function

   on Sep 25, 2026