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

[CAMEL-18555] Replace Shrinkwrap with maven-resolver #8501

Merged
merged 5 commits into from
Oct 11, 2022

Conversation

grgrzybek
Copy link
Contributor

No description provided.

@github-actions
Copy link
Contributor

⚠️ This PR changes Camel components and will be tested automatically.

@grgrzybek
Copy link
Contributor Author

It's quite complex, but that's what Shrinkwrap was doing under the covers. Now we use maven-resolver (latest version 1.8.2) directly.
I squashed several commits, but I wanted to keep the one introducing org.apache.camel.main.injection.DIRegistry as separate one.

@davsclaus
Copy link
Contributor

Really great work, its a lot of code to use the real maven for dependency resolution. And now it will work even better with using maven security settings. Thanks for adding the docs for that too.

@davsclaus
Copy link
Contributor

I think one of the classes takes 1st place for the most java imports ;)

@github-actions
Copy link
Contributor

❌ Finished component verification: 1 component(s) test failed out of 1 component(s) tested

…nject annotated beans

The purpose is to be able to configure org.eclipse.aether.RepositorySystem without
the use of deprecated (MRESOLVER-157) ServiceLocator API.
…Shrinkwrap

[CAMEL-18555] Working MavenDependencyResolverTest that uses maven-resolver without ServiceLocator

[CAMEL-18555] Full MavenDependencyResolverTest with settings, mirrors and encryption
@github-actions
Copy link
Contributor

✔️ Finished component verification: 0 component(s) test failed out of 1 component(s) tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants