You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
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.
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.
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?
The text was updated successfully, but these errors were encountered: