Re: [DISCUSS] Next release should a pre Maven 4.0.0

Please provide two PRs: 1. Update all references from 3.7.0 to 4.0.0 in core 2. Update all references from 3.7.0 to 4.0.0 in ITs Am 2020-11-26 um 19:42 schrieb Robert Scholte: Based on the responses it looks like most agree on moving forward to Maven 4. Regarding the concerns of Karl Heinz I agr

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Based on the responses it looks like most agree on moving forward to Maven 4. Regarding the concerns of Karl Heinz I agree with Michaels proposal: If there is a real need for Maven 3.7.0, let's cherry-pick those commits we want to include. I'll update the version tomorrow and rename the versions

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Le lundi 16 novembre 2020, 17:15:39 CET Michael Osipov a écrit : > Am 2020-11-13 um 18:31 schrieb Karl Heinz Marbaise: > > Hi, > > > > On 12.11.20 20:00, Robert Scholte wrote: > >> Hi, > >> > >> It is already several years ago where we started discussing about > >> Maven Next Generations. > >> Cl

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Hi, as an avid user and writer of plugins. I strongly prefer smaller releases. They are easier to adopt. As an example the first 4.0 to only bring a few potentially breaking changes looks very good to me. I understand that the release process involves a significant amount of work. Many thanks for

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Am 2020-11-13 um 18:31 schrieb Karl Heinz Marbaise: Hi, On 12.11.20 20:00, Robert Scholte wrote: Hi, It is already several years ago where we started discussing about Maven Next Generations. Clearly we needed to work on the pom, because over time we're facing more and more limitations. For (

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Thanks and +1 Le dim. 15 nov. 2020 à 20:01, Michael Osipov a écrit : > Am 2020-11-15 um 19:51 schrieb Romain Manni-Bucau: > > Le dim. 15 nov. 2020 à 19:36, Michael Osipov a > écrit : > > > >> Am 2020-11-15 um 17:26 schrieb Romain Manni-Bucau: > >>> Do we have some links/pointers on "removing pl

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Am 2020-11-15 um 19:51 schrieb Romain Manni-Bucau: Le dim. 15 nov. 2020 à 19:36, Michael Osipov a écrit : Am 2020-11-15 um 17:26 schrieb Romain Manni-Bucau: Do we have some links/pointers on "removing plugins from parent pom"? Just want to ensure it does not fall in user land but something

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Le dim. 15 nov. 2020 à 19:36, Michael Osipov a écrit : > Am 2020-11-15 um 17:26 schrieb Romain Manni-Bucau: > > Do we have some links/pointers on "removing plugins from parent pom"? > Just > > want to ensure it does not fall in user land but something internal. > > There is a JIRA issue and the s

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Am 2020-11-15 um 17:26 schrieb Romain Manni-Bucau: Do we have some links/pointers on "removing plugins from parent pom"? Just want to ensure it does not fall in user land but something internal. There is a JIRA issue and the section has been explicitly marked as deprecated for years. ---

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Am 2020-11-15 um 17:03 schrieb Hervé BOUTEMY: Le vendredi 13 novembre 2020, 19:28:20 CET Michael Osipov a écrit : Am 2020-11-13 um 19:24 schrieb Robert Scholte: Removing release profile should be combined with fail on missing/unknown profile of MNG-6012 Agreed, Karl just needs to complete his

Re: [DISCUSS] Next release should a pre Maven 4.0.0

very good idea such an alpha will also be the opportunity to test MNG-5001 = really check @readonly Mojo parameter, with warning instead of failure, because it seems there are unexpected side effects for example on maven-site-plugin Regards, Hervé Le jeudi 12 novembre 2020, 20:00:21 CET Rober

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Do we have some links/pointers on "removing plugins from parent pom"? Just want to ensure it does not fall in user land but something internal. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Le vendredi 13 novembre 2020, 19:28:20 CET Michael Osipov a écrit : > Am 2020-11-13 um 19:24 schrieb Robert Scholte: > > Removing release profile should be combined with fail on missing/unknown > > profile of MNG-6012 > Agreed, Karl just needs to complete his implementation. > > > Remove plugin se

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Am 2020-11-13 um 19:24 schrieb Robert Scholte: Removing release profile should be combined with fail on missing/unknown profile of MNG-6012 Agreed, Karl just needs to complete his implementation. Remove plugin section in super POM should be fine, now that Hervé has added warnings for it.

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Removing release profile should be combined with fail on missing/unknown profile of MNG-6012 Remove plugin section in super POM should be fine, now that Hervé has added warnings for it. There should be a default repository: central. I guess you want to move it to conf/settings.xml in the distrib

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Hi, On 12.11.20 20:00, Robert Scholte wrote: Hi, It is already several years ago where we started discussing about Maven Next Generations. Clearly we needed to work on the pom, because over time we're facing more and more limitations. For (Maven) Central the Model 4.0.0 will be required pom f

Re: [DISCUSS] Next release should a pre Maven 4.0.0

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 M

Re: [DISCUSS] Next release should a pre Maven 4.0.0

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. Reus

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Does this mean that we can finally drop deprecated stuff and even break compat? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: [DISCUSS] Next release should a pre Maven 4.0.0

@Robert: agree and we must move forward, just wanted to put a small warning we shouldn't release just to let it go out but more to ensure it is adopted in good conditions Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: [DISCUSS] Next release should a pre Maven 4.0.0

This is a good topic, but I suggest to start a different thread for it, so we can focus here on the version. Main question is: are there concerns about moving the version of Maven on master to 4.0.0? thanks, Robert On 13-11-2020 08:20:25, Romain Manni-Bucau wrote: Hmm, this is used by several t

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Hmm, this is used by several testing tools and static analyzis tools so the new pom should likely be at least next to this one but not replace it, like META-INF/maven/{G}/{A}/pom.original.xml. Flattening dependencies will likely speed up some tools parsing poms but tools also parse parent gav and m

Re: [DISCUSS] Next release should a pre Maven 4.0.0

The pom next to the artifact will be correct and ready to be consumed. Only the /META-INF/maven/{G}/{A}/pom.xml will now be the local pom. If you make use of some new features this pom might be incomplete, but AFAIK there are only a few cases where this embedded pom is used. Robert On 12-11-2020

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Le jeu. 12 nov. 2020 à 22:14, Robert Scholte a écrit : > The discussion is first of all saying the next release should be > 4.0.0-alpha-1 (or something similar), so 3.6.3 was the last of the Maven 3 > releases unless we need to backport security fixes. > What to add to that release is the next di

Re: [DISCUSS] Next release should a pre Maven 4.0.0

The discussion is first of all saying the next release should be 4.0.0-alpha-1 (or something similar), so 3.6.3 was the last of the Maven 3 releases unless we need to backport security fixes. What to add to that release is the next discussion.  Signing is only relevant for releases, but I think m

Re: [DISCUSS] Next release should a pre Maven 4.0.0

The Dependency Resolution Strategy must exist somewhere Maven Artifact Resolver, my guess is the org.eclipse.aether.collection package. On 12-11-2020 21:41:57, Andres Almiray wrote: Hi Robert, Understood. I remember our discussion at JAlba last year about the resolution strategy options at hand.

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Hmm, if it does not work e2e then even an alpha is pointless cause nobody can test it further than a hello world, was my point. Le jeu. 12 nov. 2020 à 21:01, Robert Scholte a écrit : > I don't expect that signing will work with the the first alpha, but that > shouldn't stop us of collecting feed

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Hi Robert, Understood. I remember our discussion at JAlba last year about the resolution strategy options at hand. Do you think it would be possible to expose the resolution strategy hooks in a way that may be overridden by an extension/plugin? That way alternate RS can be prototyped and tested d

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Hi Andres, BanDuplicatePomDependencyVersions is easy to add. IIRC now it is a warning, I don't mind changing it to make it break the build. DependencyConvergence is way too difficult to achieve with the larger projects. RequireUpperBoundDeps sounds reasonable as warning, although I'm sure if th

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Woohoo! While I'd love for Maven moving forward to 4 I was hoping to see the enforcer plugin (or at least some of its rules) baked into core, for example BanDuplicatePomDependencyVersions DependencyConvergence RequireUpperBoundDeps I'm sure that enabling these rules by default will break thousan

Re: [DISCUSS] Next release should a pre Maven 4.0.0

I don't expect that signing will work with the the first alpha, but that shouldn't stop us of collecting feedback. Also we need to have a look at all plugins that do something with the pom, like every packaging plugin, maven-source-plugin, maven-release-plugin to ensure the "right" pom is added.

Re: [DISCUSS] Next release should a pre Maven 4.0.0

Did we already do mvn or mvn plugins (multimodules) release with the consumer/producer pom feature? If so +1 to do a v4 with this new feature "for us" and v5 with real user features and align it with the xsd. Le jeu. 12 nov. 2020 à 20:00, Robert Scholte a écrit : > Hi, > > It is already several

[DISCUSS] Next release should a pre Maven 4.0.0

Hi, It is already several years ago where we started discussing about Maven Next Generations. Clearly we needed to work on the pom, because over time we're facing more and more limitations. For (Maven) Central the Model 4.0.0 will be required pom format, there's no discussion about that. So we