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

Muzzle plugin is not working unless maven repositories is declared explicitly #6927

Closed
aaron-ai opened this issue Oct 20, 2022 · 4 comments
Closed
Labels
bug Something isn't working

Comments

@aaron-ai
Copy link
Member

aaron-ai commented Oct 20, 2022

After #6796 , the default maven repository is removed, it seems that it causes the muzzle plugin unable to work as normal unless explicit maven repository is declared in each project. Is it by design?

@aaron-ai aaron-ai added the bug Something isn't working label Oct 20, 2022
@mateuszrzeszutek
Copy link
Member

Hey @aaron-ai ,
After #6796 the muzzle plugin will use your project.repositories settings; this is by design - we want the plugin to use the same repositories that are used during other build actions that require dependency resolution, e.g. compilation. Did you make sure to add maven central there?

@aaron-ai
Copy link
Member Author

@mateuszrzeszutek It means each instrumentation should add maven central to their build.gradle.kts?

@mateuszrzeszutek
Copy link
Member

You need to add the repositories that you want muzzle to scan - if the artifacts that you're instrumenting are hosted on maven central, then you'll need to add maven central.

@aaron-ai
Copy link
Member Author

You need to add the repositories that you want muzzle to scan - if the artifacts that you're instrumenting are hosted on maven central, then you'll need to add maven central.

Got it, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants