[MNG-4963] Parent POM not downloaded when settings define global mirr…#96
Open
[MNG-4963] Parent POM not downloaded when settings define global mirr…#96
Conversation
…or and one snapshot repo but no other release repository This IT was written with implicit black magic in mind. A mirror simply exchanges a URL of repo with another one while retaining the entire config for releases/snapshots. Logically this IT should have failed because there is no release repo. But it works because Maven adds Maven Central internally which is a release repo. For MNG-4645 one has to add a release repo in the settings to mimic that behavior. This closes #96
8 tasks
Member
Author
|
@gnodet Is this and its ticket obsolete with the move of Central out of core? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…or and one snapshot repo but no other release repository
This IT was written with implicit black magic in mind. A mirror simply exchanges
a URL of repo with another one while retaining the entire config for
releases/snapshots. Logically this IT should have failed because there is no
release repo. But it works because Maven adds Maven Central internally which is
a release repo. For MNG-4645 one has to add a release repo in the settings to
mimic that behavior.
This closes #96