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
Maven recently started alerting to move maven artifacts to provided scope so the m2 repository is not cluttered with unnecessary maven artifacts and resulting transients that are already present with maven being used. This looks to affect only maven-plugin-api in this project that is currently set to runtime and should be provided instead. I don't work with gradle so unsure of changes needed to make that happened but wondered if that could be addressed in next release?
The text was updated successfully, but these errors were encountered:
philwebb
changed the title
maven core artifacts should be moved to provided scope for the maven plugin
Move core Maven artifacts to the provided scope for the maven plugin
Jan 24, 2022
Maven recently started alerting to move maven artifacts to provided scope so the m2 repository is not cluttered with unnecessary maven artifacts and resulting transients that are already present with maven being used. This looks to affect only maven-plugin-api in this project that is currently set to runtime and should be provided instead. I don't work with gradle so unsure of changes needed to make that happened but wondered if that could be addressed in next release?
The text was updated successfully, but these errors were encountered: