Maven remote index migration and refactoring #7976
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
refactoring: split
NexusRepositoryIndexerImpl
to make it more maintainableNexusRepositoryQueries
NexusRepositoryIndexManager
automatically move remote maven index from old into current cache, if:
note:
this isn't well tested yet.
-J-Dmaven.indexing.diag.release=25
can be used to simulate a release version (would move the index from <25 into the cache forcurrent
if above conditions apply)