Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MNG-4347] Set the profiles on reecursive dependencyManagement imports #158

Conversation

clarkperkins
Copy link

When a set of default repositories are specified via a profile in the global settings.xml, recursive dependencyManagement imports cannot be resolved from repositories in the profiles, since the profiles are not currently passed along to the ModelBuildingRequest used for resolving recursive imports. This adds the profile to that ModelBuildingRequest.

@clarkperkins clarkperkins changed the title Set the profiles on reecursive dependencyManagement imports [MNG-4347] Set the profiles on reecursive dependencyManagement imports Feb 16, 2018
@clarkperkins
Copy link
Author

clarkperkins commented Feb 16, 2018

I just found this issue in jira, added the ticket number

@clarkperkins
Copy link
Author

Looks like there's a better solution out there for this, I'm going to close this.

pzygielo pushed a commit to pzygielo/maven that referenced this pull request Jan 4, 2023
gnodet pushed a commit to gnodet/maven that referenced this pull request Nov 20, 2024
…apache#158)

An IT for Maven 3.9+ that "exercise" both resolver transport: wagon and native (so we have 2 tests both forcing transport with `-Dmaven.resolver.transport` one wagon (which is default, but setting is there to be explicit) and once native.

It builds a project that needs a plugin (to pull it will use set transport), and that plugin will use resolver as well to resolve set artifact. If any of these fails, maven project fails.

Related fix: apache#732 (jn maven-3.9.x and master)
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.

1 participant