Re: Maven 4.0.0 Release - Thoughts?
Am 22.05.2025 um 09:23 schrieb Hervé Boutemy: yes to try to make sure Maven 4.0.0 will run smoothly on Java 24 on tying Maven 4.0.0 release to Jira to GH Issues migration: is there a strong reason for coupling these 2 huge beasts? Hi Hervè, TLDR: No strong reason ;) Long version: Maybe I was not clear with my suggestion. I don't want to coupling the full migration including moving JIRA issues to Github, but to discuss if we want to finish to enable github issues on all repositories, so people can more easy report issues to us (which was one of the pros in the discussion to use GH issues) as I personally believe that, when Maven 4 is out, there will be more users who want to provide. Current stand (if I not miscounted) 21 repositores are left to ENABLE issues. I will work on further at the weekend so I think we will be done soon with that. Migration of existing JIRA is another story, which comes after that but which is not part of my suggestion. Greetings Matthias - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 4.0.0 Release - Thoughts?
Le jeudi 22 mai 2025, 17:30:20 CEST Matthias Bünger a écrit : > Am 22.05.2025 um 09:23 schrieb Hervé Boutemy: > > yes to try to make sure Maven 4.0.0 will run smoothly on Java 24 > > > > on tying Maven 4.0.0 release to Jira to GH Issues migration: is there a > > strong reason for coupling these 2 huge beasts? > > Hi Hervè, > > TLDR: No strong reason ;) > > Long version: Maybe I was not clear with my suggestion. I don't want to > coupling the full migration including moving JIRA issues to Github, but > to discuss if we want to finish to enable github issues on all > repositories, so people can more easy report issues to us (which was one > of the pros in the discussion to use GH issues) as I personally believe > that, when Maven 4 is out, there will be more users who want to provide. so finally there is a (not so bad) reason: anticipating feedback when Maven 4 is out (with the complexity of creating a Jira accounts = why we started the move) > > Current stand (if I not miscounted) 21 repositores are left to ENABLE > issues. I will work on further at the weekend so I think we will be done > soon with that. Migration of existing JIRA is another story, which comes > after that but which is not part of my suggestion. it seems the only answer is "let's go faster": I won't fight, it seems I'm alone, and the target is necessary I'll try to do a release of something, and I'll see if I'm over cautious. On activating on Maven core (and blocking new issues on Jira), I'll let the big committers on it decide > > Greetings > > Matthias > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 4.0.0 Release - Thoughts?
Sounds like a good plan! On Wed, 21 May 2025 at 4:12 pm, Guillaume Nodet wrote: > Hey Maven Devs, > > We're gearing up to release a new version from the master branch. I'm > thinking we should go for 4.0.0 instead of rc-4. What do you all think? Any > feedback or ideas on the versioning or release plan? Let’s hear it! > > Cheers, > > Guillaume >
Re: Maven 4.0.0 Release - Thoughts?
On Thu, 22 May 2025 at 09:24, Hervé Boutemy wrote: > yes to try to make sure Maven 4.0.0 will run smoothly on Java 24 > > on tying Maven 4.0.0 release to Jira to GH Issues migration: is there a > strong > reason for coupling these 2 huge beasts? > > > longer analysis: > > Jira to GH Issues migration has started everywhere (66 as of now, if > tracking > is accurate [1]), but near nothing is finished > First step - switch to GitHub was done in many projects > > concretely: how many releases of simple plugins or components have been > done > with GH Issues and associated release notes prepared by the new approach? > and > what if I add "by people other than Slawek"? > hint: [2] > Another question: how many releases do we have at all? And yes if something in a new way is not clear we need to work on it. > We have so many small plugins or components to get experience. I expected > that > by mid-may we would have huge experience with the new approach: that's not > the > case > > Maven core is the biggest, most complex, migration we have: I'd be > seriously > worried if we couple the Maven 4.0.0 release with Jira to GH Issues > migration > > Regards, > > Hervé > > > [1] https://cwiki.apache.org/confluence/display/MAVEN/ > JIRA+to+GitHub+Issues+switching > > [2] > https://lists.apache.org/list?dev@maven.apache.org:lte=1M:[VOTE]%20Release > > Le mercredi 21 mai 2025, 22:03:06 CEST Matthias Bünger a écrit : > > Hey, > > I‘ve lost the overview to the java 24 issues, but if I got it right the > sisu > > 0.94 can handle it. So if we are fine on running on java 24 and our 4.x > > plugins (there are some in beta etc, look at the update parent to 44 of > > source-p for example) are final too, I think we are good to go. Why the > > plugins? Think it’s not good to say „here main is final, use the 4.x > > plugins of those exist, bit yes they are alpha/beta“. > > > > Another point we can consider: finish enable github issues for all > relevant > > projects to make it easier and consisten for users to provide > > feedback/issues. Slawek and I are close to finish. If I have it in mind > > correctly about 15 repos left, including maven itself (long standing > draft > > afair). > > > > Have a good night everyone. > > Matthias > > > > Sent from mobile > > > > > Am 21.05.2025 um 08:12 schrieb Guillaume Nodet : > > > > > > Hey Maven Devs, > > > > > > We're gearing up to release a new version from the master branch. I'm > > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? > > > Any > > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > > > Cheers, > > > > > > Guillaume > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
Re: Maven 4.0.0 Release - Thoughts?
On 2025/05/21 09:05:07 Guillaume Nodet wrote: > Hi all, > > I have several significant features waiting as PRs (mixins and > cascading profiles), but I’ve decided to postpone them until 4.1.0. > For what it’s worth, several people, including the IntelliJ team, have > expressed concerns about 4.0.0 being a moving target due to the > continuous addition of new features in RCs. This is fine. > I’d prefer to release 4.0.0 with a limited set of new features to > ensure stability and reserve the larger changes for 4.1.0, which we > could target for the end of year. This could also include the upgrade > to JDK 21 since JDK 25 should be released in September. OK as well to push to 4.1.0, but raising requirements is another discussion. > Best, > Guillaume Nodet > > Le mer. 21 mai 2025 à 10:13, Michael Osipov a écrit : > > > > On 2025/05/21 06:11:42 Guillaume Nodet wrote: > > > Hey Maven Devs, > > > > > > We're gearing up to release a new version from the master branch. I'm > > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? > > > Any > > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > Slawek is working on a bigger new feature which deserves another RC... > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- > > Guillaume Nodet > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 4.0.0 Release - Thoughts?
Le jeudi 22 mai 2025, 08:49:20 CEST Mark Derricutt a écrit : > On 22 May 2025 at 6:19:26 PM, Hervé Boutemy wrote: > > I don't get what plugin updates are expected: are there Maven 3 plugins > > known > > to fail on Maven 4? If yes, are they so many? > > That I’m not sure - since we can’t run our builds under Maven 4 (tiles, > mixins, the problems of my ownn makings) I’ve not really tried M4 outside > of small projects. > > I should check the OSGi bundle-maven-plugin along with the ANTLR plugins we > use. we'll probably need to clearly track somewhere I absolutely want to avoid the masses to feel they are forced to maintain a Maven 4-specific plugin fork: Maven 4 API is the future, yes, but the path is expected to be smooth with Maven 3 plugin API compatibility = that's the intent AFAIK: I hope the actual result will match the intent - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 4.0.0 Release - Thoughts?
yes to try to make sure Maven 4.0.0 will run smoothly on Java 24 on tying Maven 4.0.0 release to Jira to GH Issues migration: is there a strong reason for coupling these 2 huge beasts? longer analysis: Jira to GH Issues migration has started everywhere (66 as of now, if tracking is accurate [1]), but near nothing is finished concretely: how many releases of simple plugins or components have been done with GH Issues and associated release notes prepared by the new approach? and what if I add "by people other than Slawek"? hint: [2] We have so many small plugins or components to get experience. I expected that by mid-may we would have huge experience with the new approach: that's not the case Maven core is the biggest, most complex, migration we have: I'd be seriously worried if we couple the Maven 4.0.0 release with Jira to GH Issues migration Regards, Hervé [1] https://cwiki.apache.org/confluence/display/MAVEN/ JIRA+to+GitHub+Issues+switching [2] https://lists.apache.org/list?dev@maven.apache.org:lte=1M:[VOTE]%20Release Le mercredi 21 mai 2025, 22:03:06 CEST Matthias Bünger a écrit : > Hey, > I‘ve lost the overview to the java 24 issues, but if I got it right the sisu > 0.94 can handle it. So if we are fine on running on java 24 and our 4.x > plugins (there are some in beta etc, look at the update parent to 44 of > source-p for example) are final too, I think we are good to go. Why the > plugins? Think it’s not good to say „here main is final, use the 4.x > plugins of those exist, bit yes they are alpha/beta“. > > Another point we can consider: finish enable github issues for all relevant > projects to make it easier and consisten for users to provide > feedback/issues. Slawek and I are close to finish. If I have it in mind > correctly about 15 repos left, including maven itself (long standing draft > afair). > > Have a good night everyone. > Matthias > > Sent from mobile > > > Am 21.05.2025 um 08:12 schrieb Guillaume Nodet : > > > > Hey Maven Devs, > > > > We're gearing up to release a new version from the master branch. I'm > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? > > Any > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > Cheers, > > > > Guillaume > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 4.0.0 Release - Thoughts?
I would go for rc4 because we still have API changes after rc3 and our plugins needs adjustments that could again require another, smaller changes. With current state of plugins 4.x they can't be used with latest (master) version so we could offer only 3.x for Maven 4. Not so big issue for many users but without semi automatic way to move plugin to new public API we are selling new "untested internally". In my opinion, if we could have releases of core plugins based on rc4 API and our CI/CD pipelines runs also under Maven 4 - it would be safer. Sylwester śr., 21 maj 2025, 08:12 użytkownik Guillaume Nodet napisał: > Hey Maven Devs, > > We're gearing up to release a new version from the master branch. I'm > thinking we should go for 4.0.0 instead of rc-4. What do you all think? Any > feedback or ideas on the versioning or release plan? Let’s hear it! > > Cheers, > > Guillaume >
