Skip to content

[MNG-4347] import-scoped dependencies of direct dependencies are not resolved using profile modifications from settings.xml#159

Open
clarkperkins wants to merge 2 commits intoapache:masterfrom
clarkperkins:bugfix/MNG-4347-recursive-imports
Open

[MNG-4347] import-scoped dependencies of direct dependencies are not resolved using profile modifications from settings.xml#159
clarkperkins wants to merge 2 commits intoapache:masterfrom
clarkperkins:bugfix/MNG-4347-recursive-imports

Conversation

@clarkperkins
Copy link
Copy Markdown

@clarkperkins clarkperkins commented Feb 16, 2018

o Updated the 'DefaultModelResolver' to handle replacing repositories the same way the
'DefaultDependencyCollector' does. When the 'DefaultDependencyCollector' finds
a repository in a child node with an id matching a repository already in use,
it will only merge any mirror definitions but never change the repository already
in use. The 'DefaultModelResolver' needs to follow the same logic. What has been
provided must not change for consistency.

Cherry-picked from @ChristianSchulte's fork, per comment on the MNG-4347 ticket. I made the same changes to the ProjectModelResolver, since it seems that's the implementation that's getting used by the dependencyManagement import resolution rather than the DefaultModelResolver.

ChristianSchulte and others added 2 commits February 16, 2018 11:43
…resolved using profile modifications from settings.xml

o Updated the 'DefaultModelResolver' to handle replacing repositories the same way the
  'DefaultDependencyCollector' does. When the 'DefaultDependencyCollector' finds
  a repository in a child node with an id matching a repository already in use,
  it will only merge any mirror definitions but never change the repository already
  in use. The 'DefaultModelResolver' needs to follow the same logic. What has been
  provided must not change for consistency.
@clarkperkins clarkperkins changed the title Bugfix/mng 4347 recursive imports [MNG-4347] import-scoped dependencies of direct dependencies are not resolved using profile modifications from settings.xml Feb 16, 2018
pzygielo pushed a commit to pzygielo/maven that referenced this pull request Jan 4, 2023
* fix paring version problem in no-overwrite tests

* fix no-overwriten tests when running in  windows

* fix bug resulting from line seperator difference in Windows

* remove redundant code

* fix the version position problem

Co-authored-by: yangnuoyu <yangnuoyu@penguin>
gnodet pushed a commit to gnodet/maven that referenced this pull request Nov 20, 2024
The HttpServer helper is used by two ITs:
* MavenITmng7470ResolverTransportTest
* MavenITmng5771CoreExtensionsTest

And it logs in case of MNG7470 for unknown reason. My bet would
be some static initing happening as side effect of OTHER ITs that
use Jetty directly, like MavenITmng5868NoDuplicateAttachedArtifacts.

Anyway, this sorts out Jetty logging.
gnodet pushed a commit to gnodet/maven that referenced this pull request Nov 20, 2024
Fix for apache#159

Jetty logger not always is StdErrLog can be eg. Slf4jLog
@jira-importer
Copy link
Copy Markdown

Resolve #5813

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants