Re: [VOTE] Release Apache Maven 3.9.7
+1 (not binding) ran the NB tests against staged lib and tested it a bit manually too - all good! https://github.com/apache/netbeans/actions/runs/9190011942 -mbien On 22.05.24 12:09, Tamás Cservenák wrote: Howdy, We solved 21 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353964 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2125/ Dev dist directory (binary bundles updated): https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.7/ Source release checksums: apache-maven-3.9.7-src.tar.gz.sha512 a3c211ce683afbde9c4becf8b32397d14d3e7d8e8261094da037dcf27a697a93134440e055e7a9e7e26af2db543d4d9c4e7b0296560f5193df7ba90b9a68d1d1 apache-maven-3.9.7-src.zip.sha512 cdd8249807e251d07c613a65120058993e47a4cbf7f6dbda8599c7ca7ab4ed3fedc727e651f43cba0e9b0d604055c1106c1243be64a1d52c5ddf72dbec5e65dc Staged site: https://maven.apache.org/ref/3-LATEST/ Draft for release notes: https://github.com/apache/maven-site/pull/521 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72h [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Require Java 17 for Maven 4
+1 (non-binding; for JDK 17 or 21) leaving JDK 8 behind is an important step for the java community. -mbien On 28.02.24 08:30, Benjamin Marwell wrote: Hi Maven Devs/Users/Committers and PMC members! After several discussions on the mailing lists, I would like to start a vote in favour of setting the minimal Java bytecode target of Maven-Core 4 to 17 and hence require Java 17 for Maven 4. This is a procedural majority vote [1*]: You can also vote with fractions and negative votes are not vetoes. Please also notice: * Maven 3 will stay at Java 8 no matter what. * We may raise Maven 4 to JDK 21 later if we feel like it (depending on the release date). This is not part of this vote. * The linked PR is not part of this vote (this is not a code vote). But you may take a look at it to understand the intended change. PR: https://github.com/apache/maven/pull/1430 Maven-Parent will not be raised with this vote, the other PR is not part of this vote. Please refrain from starting discussions in this thread, but do include a reasoning on downvotes and feel free to start a new discussion on the mailing list, or comment on the existing ones. --- Vote open for 72 hours: [ ] +1 (set JDK17 min version for Maven 4.x) [ ] +0 [ ] -1 (please include reasoning) --- - Ben [1*]: https://www.apache.org/foundation/voting.html - 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: [DISCUSS] Java version for Maven
On 23.02.24 01:42, Hunter C Payne wrote: The performance benefits aren't provided by the compiler, they come from hotspot and that's the JVM version at runtime that matters there. this is only partially correct. Many optimizations are based on invokedynamic which only exists post bytecode level 9. A whole category of String related optimizations unlocks simply by recompiling something with --release 11 or later. Running on a more modern JVM without the bytecode level bump, won't help in that case. There are also hundreds of behind the scenes optimizations which are unlocked for free just by using new API. For example stream.transferTo() is going to be not only more convenient and less error prone, but also likely more efficient than the dozens of stream copy variations which show up in projects (why? because it takes into account what exact streams/channels etc are involved). If you see a new method in the JDK: there is probably a reason why it was introduced. That being said: in discussions like this, focusing on individual features is often not helpful. Since the next post will be likely about "I don't care about 1-10% faster/more memory efficient String concatenation in my CI build since at my current gig we get CI for free due to the geothermal power plant in the backyard". From a birds eye view projects fall into two categories: a) short living projects which die on JDK X within the lifespan of JDK X. This is a completely valid strategy since it is often known that something is going to be rewritten from scratch, not needed anymore or replaced at some point in future. b) long living projects which will have to upgrade, since projects don't exist in a vacuum. The environment moves on, JDK X compatible dependencies which still get security updates will disappear at some point etc etc. I would assume that it is not controversial to call maven a long living project. So this discussion here should be about: when is the best time to bump the JDK version - I would argue that maven 4 is pretty good timing! If you want maven on JDK 8 till 2030+, I would be curious about two things: - why can't you use maven 3.x? - what exactly *should* happen after 2030+? Should maven die (is mvn category a) after all?)? Should there be a jump from 8 to JDK 3x and the community should deal with all the piled up problems all at once? Why is delaying this event the better strategy when compared to incremental steps? What is the JDK 8 exit strategy? best regards, -mbien
Re: [VOTE] Release Maven Indexer 7.1.2
+1 (not binding) Hi! tested via https://github.com/apache/netbeans/pull/6935 best regards && happy new year, michael On 08.01.24 12:03, Tamás Cservenák wrote: Howdy, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12354029 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MINDEXER/issues Staging repository: https://repository.apache.org/content/repositories/maven-2060 Source release SHA512: 427f2330e927760556fde25b5561e8969380f7c381ecbf5f76513ca7689fbcb971d9482876765dbf82ee90d350c59d7281cbc31555e7f967495ac293f555658c Staging site: https://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Indexer 7.1.1
+1 (not binding) Hi, ran the NB tests here https://github.com/apache/netbeans/pull/6791 using the staged build of maven-indexer 7.1.1 and everything was fine. (did also some manual testing) thanks for the release && best regards, michael On 15.12.23 19:31, Sylwester Lachiewicz wrote: +1 Sylwester pt., 15 gru 2023, 19:25 użytkownik Slawomir Jaranowski < s.jaranow...@gmail.com> napisał: +1 śr., 13 gru 2023 o 23:53 Tamás Cservenák napisał(a): Howdy, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12353771 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MINDEXER/issues Staging repository: https://repository.apache.org/content/repositories/maven-2045 Source release SHA512: f8475c51be34b9a3ba9ab2ec062538f0a9bccfb8064cebf694c1c66687673e6ab3e19160903131ce3b5f4b4b50c329c888e2358b71c4371a20631656919df1e4 Staging site: https://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
