From the top of my head: * Remove release profile * Remove plugin section in super POM * Move Central out of Core
As well as a review of all consistency fixes to dependency resolution done by Christian Schulte.
I also agree with maven-compat. This needs to go, currently not possible due to MNG-6561.
Am 2020-11-13 um 18:11 schrieb Robert Scholte:
I'm not going to say simply yes, it probably depends. Any specific things you have in mind? Also, I don't know what to do with maven-compat. I would prefer to remove it and introduce maven-compat3 as a bucket for classes that we don't want to use in Maven 4, but can still be used by plugins. Reusing the maven-compat artifactId with a different set of classes is most likely a recipe for disaster. Robert On 13-11-2020 17:53:47, Michael Osipov <[email protected]> wrote: Does this mean that we can finally drop deprecated stuff and even break compat? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
