Re: [VOTE] Release Maven Site Plugin version 4.0.0-M15
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 29.05.24 17:19, Michael Osipov wrote: Hi, we solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12354740 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2135/ https://repository.apache.org/content/repositories/maven-2135/org/apache/maven/plugins/maven-site-plugin/4.0.0-M15/maven-site-plugin-4.0.0-M15-source-release.zip Source release checksum(s): maven-site-plugin-4.0.0-M15-source-release.zip sha512: d0abf8630845be229e3d480eb1a74cbd0f359e96418eb7ca53a799c618d2a887ae18718bc5635587e6187ab77ed65438e1b56115dec8378eee6477d8c6cab820 Staging site: https://maven.apache.org/plugins-archives/maven-site-plugin-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 Plugin Tools version 3.13.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 28.05.24 10:26, Michael Osipov wrote: Hi, we solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12354759 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2133/ https://repository.apache.org/content/repositories/maven-2133/org/apache/maven/plugin-tools/maven-plugin-tools/3.13.1/maven-plugin-tools-3.13.1-source-release.zip Source release checksum(s): maven-plugin-tools-3.13.1-source-release.zip sha512: 2464cd9e69eeaec410488228b9d1773e572ec6fbe339e745da591b2837e8ea806eaf2b57608662eee96c79a4f8f43cb4ebbcb087c2988e234ad144f08eb4c00f Staging site: https://maven.apache.org/plugin-tools-archives/plugin-tools-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 Shade Plugin 3.6.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 28.05.24 17:21, Tamás Cservenák wrote: Howdy, We solved 7 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12354611 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MSHADE/issues Staging repo: https://repository.apache.org/content/repositories/maven-2134/ Source release checksum(s) SHA-512 : b0a31f02918329c466abd9c7b0c01bc7baeb0fbf8ef084212800c24b937d01495614fde43771689daec9160ef43bcd93c2d87a12dfe9d4e0fd926e190f28f797 Staging site: https://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Javadoc Plugin version 3.7.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 29.05.24 18:18, Michael Osipov wrote: Hi, we solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12354465 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MJAVADOC/issues Staging repo: https://repository.apache.org/content/repositories/maven-2136/ https://repository.apache.org/content/repositories/maven-2136/org/apache/maven/plugins/maven-javadoc-plugin/3.7.0/maven-javadoc-plugin-3.7.0-source-release.zip Source release checksum(s): maven-javadoc-plugin-3.7.0-source-release.zip sha512: 8ab35979e8c2cc9d69578b32cb61a227a4f2071c5201b97c98ece12a0a83af95f5268489e88e26dcccba0eab940bc6ac1f4d52138e8db280d0c0a61d21a379ca Staging site: https://maven.apache.org/plugins-archives/maven-javadoc-plugin-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 Plugin Tools version 3.13.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 28.05.24 10:26, Michael Osipov wrote: Hi, we solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12354759 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2133/ https://repository.apache.org/content/repositories/maven-2133/org/apache/maven/plugin-tools/maven-plugin-tools/3.13.1/maven-plugin-tools-3.13.1-source-release.zip Source release checksum(s): maven-plugin-tools-3.13.1-source-release.zip sha512: 2464cd9e69eeaec410488228b9d1773e572ec6fbe339e745da591b2837e8ea806eaf2b57608662eee96c79a4f8f43cb4ebbcb087c2988e234ad144f08eb4c00f Staging site: https://maven.apache.org/plugin-tools-archives/plugin-tools-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 Apache Maven Enforcer version 3.5.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 26.05.24 19:51, Slawomir Jaranowski wrote: Hi, We solved 9 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12353621 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MENFORCER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2131/ https://repository.apache.org/content/repositories/maven-2131/org/apache/maven/enforcer/enforcer/3.5.0/enforcer-3.5.0-source-release.zip Source release checksum(s): enforcer-3.5.0-source-release.zip - SHA-512 : a8d91fe9f0a47746af8c0a0c9287350750dc2fc342b73f14ff9d0f32cb2b4c1c9ba727d7a5924644cd22d12bbef70474c7404d5c06858585595af085e761d095 Staging site: https://maven.apache.org/enforcer-archives/enforcer-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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: [DISCUSS] Removal of ineffective switch for Maven 4
Hi, +1 for removing them as well Kind regards Karl Heinz Marbaise On 24.05.24 13:09, Maarten Mulders wrote: On 24/05/2024 09:43, Michael Osipov wrote: On 2024/05/24 07:06:45 Maarten Mulders wrote: Hi all, Today, I noticed Maven has an `-up` switch, for `--update-plugins`. The help text says it's ineffective, only kept for backward compatibility. With the advent of Maven 4, would this be a good moment to remove this switch? There much more of them to be killed, but before we do that we need to make sure that any of our plugins which invoke Maven never pass them, then we can discuss their removal. Just checked, and indeed, there are a few more listed explicitly as "ineffective": -cpu, --check-plugin-updates -npr, --no-plugin-registry -npu, --no-plugin-updates -up, --update-plugins My idea would then be to see if any of these four are used in our own code base (core as well as plugins). If there are usages, let's remove them. That should not be hard, as they don't trigger any behaviour anymore. After that, we can continue to drop them from the Maven CLI. Would that make sense? Maarten - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Removal of `-up` switch for Maven 4
Hi, +1 for removing it... Kind regards Karl Heinz Marbaise On 24.05.24 09:06, Maarten Mulders wrote: Hi all, Today, I noticed Maven has an `-up` switch, for `--update-plugins`. The help text says it's ineffective, only kept for backward compatibility. With the advent of Maven 4, would this be a good moment to remove this switch? Thanks, Maarten - 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: [VOTE] Release Apache Maven 4.0.0-beta-3
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 22.05.24 17:12, Guillaume Nodet wrote: This is a vote to release Apache Maven 4.0.0-beta-3, as I've cut another release to fix blocking issues found in beta-2. We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354634 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MNG/issues Release candidates: https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-beta-3/ Staging repository: https://repository.apache.org/content/repositories/maven-2126/ Source release SHA512: - apache-maven-4.0.0-beta-3-src.zip 4125acba32218e341b34c1bbe7700f5aa71947fd1a6a5d418825822099800e3b798a5300eaf711e0709866b7e5fc6fee323515af18d8ab25d7eaac034d72b1c6 - apache-maven-4.0.0-beta-3-src.tar.gz 8ca063a72fdacbcbe4afc33fc46e6c8920327092d11f3d8a77723ce995c3e24d1e8413cce3d5bc59a47657316834bfb9d4706d8bdffa5da5e147bcb404381808 Staging site: https://maven.apache.org/ref/4-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html The vote is open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Guillaume Nodet - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.9.7
Hi, +1 from me. Kind regards Karl Heinz Marbaise 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] Release Apache Maven Wrapper 3.3.2
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 21.05.24 17:17, Tamás Cservenák wrote: Howdy, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12354608 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MWRAPPER/issues Staging repo: https://repository.apache.org/content/repositories/maven-2124/ Source release checksum SHA512: 620d6945ad3a18cc80da52ad81af452524cf427b24adcff1a83ad77a0d0e72dd18825e2c5e4405e43babe8e6fd52e83cef58b10d39b55fa8a4bba9a7801d66a5 Staging site: https://maven.apache.org/wrapper-archives/wrapper-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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: Road forward for: New flag to verify the status
Hi, the issue I see with implementing it either in core/plugin/extension that this is a kind of burrow where are so many situation which you can't even handle correctly Using a plugin means you have to be sure that plugin has been download upfront. For a remote repository and calling the first time or alike that simply does not work... (circular dependency).. If you like to use an extension the same... If you like to enhance the core there are so many different situation I would say it's not worth the effort... My suggestion is it make a list of possible issues in the error message for example: - have you check the network connection - Is the local repository accessible (permission) - etc. to summarize that: - creating a better error message... (with possible suggestions what to check) Kind regards Karl Heinz Marbaise On 26.04.24 16:11, Juul Hobert wrote: Hi, It's been a while since changes have been made to MNG-6869. It adds helpful functionality that is particularly useful when you're on a company network and want to do some basic checks to verify if Maven is working. This will be helpful for a large group of users and helps in solving basic issues and therefore could reduce false issues being reported about "Maven not working". The pull request unsatisfyingly ended up in a discussion where three flavors came across: implement it in core, in a plugin or in an extension. In summary the following arguments apply to the three different flavors: Move it to a plugin + Does not introduce extra complexity in core - Needs additional downloads and could fail before the basic checks occur Move it to an extension + Does not introduce extra complexity in core - Requires additional installation steps before it can be used (we could consider to ship the extension with Maven to circumvent that) Put it in core + Works without requiring additional downloads / installation steps + Can do all basic checks I like to know how the community thinks about this, so please reply briefly with the following if you have a opinion about it: - "1" for plugin - "2" for extension - "3" for core - "4" drop the idea, close the ticket I'm planning to work on it on the 10th of May and would like to continue working on it then. I would appreciate it if replies are given before this date. Cheers Juul Hobert, also on behalf of Giovanni van der Schelde - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.14.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 12.05.24 22:40, Slawomir Jaranowski wrote: Hi, We solved 10 issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20fixVersion%20%3D%2012353840%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-dependency-analyzer Staging repo: https://repository.apache.org/content/repositories/maven-2115/ https://repository.apache.org/content/repositories/maven-2115/org/apache/maven/shared/maven-dependency-analyzer/1.14.0/maven-dependency-analyzer-1.14.0-source-release.zip Source release checksum(s): maven-dependency-analyzer-1.14.0-source-release.zip - SHA-512 : 177624ae1f2cff0a05bd694a70f7e139f7cad79db63287644dfbf307cc5be09624202f2ff00f16125926a4614553065603eb61143f690bf38e347ff6b2d00282 Staging site: https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven 4.0.0-beta-2
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 13.05.24 19:40, Guillaume Nodet wrote: I've cut another release after having fixed a bug in the consumer pom creation. This is a vote to release Apache Maven 4.0.0-beta-1. We solved 21 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922= 12354392 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354392> There are still some issues in JIRA: https://issues.apache.org/jira/projects/MNG/issues Release candidates: https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-beta-2/ Staging repository: https://repository.apache.org/content/repositories/maven-2117/ Source release SHA512: - apache-maven-4.0.0-beta-1-src.zip 0dff19216028ed7ab15914795c62a2a3247b9f45daedfd0db88266edecf97f16c888c7aac501b6b2d9373e03c828e9ba30f9837cfaafd9a4f32b04fa0776e0d3 - apache-maven-4.0.0-beta-1-src.tar.gz 04df9d340081fa5cc4c840fee4bbed0d65d2d622e9cdbc0a713438a104933485f22d31bf4b35ce695913b790cf10f11f8f31ce73e0a796debfe7fc99268d9701 Staging site: https://maven.apache.org/ref/4-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html The vote is open for at least 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 Site Plugin version 4.0.0-M14
Hi, +1 from me. Kind regards Karl Heinz Marbaise PS.: Version Number related to Maven 4 API (was already mentioned). On 05.05.24 21:29, Michael Osipov wrote: Hi, we solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12354123 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2109/ https://repository.apache.org/content/repositories/maven-2109/org/apache/maven/plugins/maven-site-plugin/4.0.0-M14/maven-site-plugin-4.0.0-M14-source-release.zip Source release checksum(s): maven-site-plugin-4.0.0-M14-source-release.zip sha512: cf9b896e1bc10b0bb81ded66f343e478da4da21300d10ac586ac08a8640bc7c11f25ff49d8f443c12e98011608c5d2db308d9b0b7ec1d9378d84616712b5b660 Staging site: https://maven.apache.org/plugins-archives/maven-site-plugin-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven PMD Plugin version 3.22.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 18.04.24 12:38, Andreas Dangel wrote: Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621=12353876=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPMD%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2095/ https://repository.apache.org/content/repositories/maven-2095/org/apache/maven/plugins/maven-pmd-plugin/3.22.0/maven-pmd-plugin-3.22.0-source-release.zip Source release checksum(s): maven-pmd-plugin-3.22.0-source-release.zip sha512: ebc08fa2b9b1c7ae3cb985d741ea2326e23752e5dabe764a213a7acca9c02287e4e15d6b274f9f8cabbc29193aaa622cbd9676a065a2cd5de7e4816eb918c0e8 Staging site: https://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 Regards, Andreas - 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: [VOTE] Apache Maven Toolchains Plugin 3.2.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 18.04.24 02:50, Olivier Lamy wrote: Hi, I'd like to release Apache Maven Toolchains Plugin 3.2.0 We fixed 7 issues. Staging repo: https://repository.apache.org/content/repositories/maven-2094/ Source release checksum SHA512: c26ee136b19220cfdde41211426432feb8b042f23d96d9c490c0befa4986c89919ba412285a8acf621a2763ccfc5b768813df84669440bdef0a805ff623ef2ca Staging site: https://maven.apache.org/plugins-archives/maven-toolchains-plugin-LATEST Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 - 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: [VOTE] Release Apache Maven Wrapper 3.3.0
Hi, +1 from me. Kind regrads Karl Heinz Marbaise On 17.04.24 21:34, Tamás Cservenák wrote: Howdy, We solved 21 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12352995 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MWRAPPER/issues Staging repo: https://repository.apache.org/content/repositories/maven-2093 Source release checksum SHA512: 4c495321f25d7001ba76a0cb4fd207b59905c4fef9066df8ca6f37eb645a74e55234710222d46df297bfd6ca17138630778ffa27c026a23e4b1045e0e98d9a04 Staging site: https://maven.apache.org/wrapper-archives/wrapper-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven JAR Plugin version 3.4.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 16.04.24 23:13, Slawomir Jaranowski wrote: Hi, We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12354551 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2092/ https://repository.apache.org/content/repositories/maven-2092/org/apache/maven/plugins/maven-jar-plugin/3.4.1/maven-jar-plugin-3.4.1-source-release.zip Source release checksum(s): maven-jar-plugin-3.4.1-source-release.zip - SHA-512 : 7a55772e85af9ce8268ab0d5792197a2341f4c49c1deeba7f8ba98c2b8d56ec3f1d6b34d79b4c4d92dee1df3e3a9e69a5b9ef8974086fa6c3785db5c6fe14e6f Staging site: https://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven GPG Plugin 3.2.4
Hi, +1 from me Kind regards Karl Heinz Marbaise On 16.04.24 15:28, Tamás Cservenák wrote: Howdy, Note: This is a bugfix release related to "best practices". We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12354486 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MGPG/issues Staging repo: https://repository.apache.org/content/repositories/maven-2091 Source release checksum SHA512: 4d6c4417744fe0bb192440f1d220c22f8601ccafbba53a261e990cff8e5fc6e25afe5376a795f77c3f5a227d8457e68558a7faff9ce0cca8242b5cfb29253f1f Staging site: https://maven.apache.org/plugins-archives/maven-gpg-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven Project Parent POMs version 42
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 13.04.24 23:31, Slawomir Jaranowski wrote: Hi, Notice: Maven ASF 32 from staging is needed for testing We solved 16 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353850 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Git diff: https://github.com/apache/maven-parent/compare/maven-parent-41...maven-parent-42 Staging repo: https://repository.apache.org/content/repositories/maven-2088/ https://repository.apache.org/content/repositories/maven-2088/org/apache/maven/maven-parent/42/maven-parent-42-source-release.zip Source release checksum(s): maven-parent-42-source-release.zip - SHA-512 : 087e93a2ce864874de6bb9aaedb91db84d1cd4a5a6b5d225de874b436c402d765978c7c18f0b4707f34935a220413089c79c15fcf17628044f943fefc61594a4 Staging site: https://maven.apache.org/pom-archives/maven-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 ASF Parent POM version 32
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 13.04.24 18:46, Slawomir Jaranowski wrote: Hi, We solved 21 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353849 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20asf%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Git diff: https://github.com/apache/maven-apache-parent/compare/apache-31...apache-32 Staging repo: https://repository.apache.org/content/repositories/orgapacheapache-1037/ https://repository.apache.org/content/repositories/orgapacheapache-1037/org/apache/apache/32/apache-32-source-release.zip Source release checksum(s): apache-32-source-release.zip - SHA-512 : a75bd6649bd665d70c00c71d64999b346b1734e148244461f1b5c7ba0de8d44021f65f6228807fac30c4d593022ac06ab887fcc4a41cc019bbef02d2d323db03 Staging site: https://maven.apache.org/pom-archives/asf-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven JAR Plugin version 3.4.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 09.04.24 23:27, Slawomir Jaranowski wrote: Hi, We solved 12 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12352303 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2085/ https://repository.apache.org/content/repositories/maven-2085/org/apache/maven/plugins/maven-jar-plugin/3.4.0/maven-jar-plugin-3.4.0-source-release.zip Source release checksum(s): maven-jar-plugin-3.4.0-source-release.zip - SHA-512 : 542c14a583dad400ca9dc64cc209144bdb539a919ddd8d8361e5ff13402605289fa3634a2cb87f2ece23f8c408275e12ac37e15a92c74ddd3a9a65d8f2954ba9 Staging site: https://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven GPG Plugin 3.2.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.03.24 09:25, Tamás Cservenák wrote: Howdy, Note: this is a bugfix release for https://issues.apache.org/jira/browse/MGPG-112 We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12354394 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MGPG/issues Staging repo: https://repository.apache.org/content/repositories/maven-2074/ Source release checksum SHA512: 19bb9d57b2caec3524ecc3abc8efb818061541874011763c474c0d60608a3b156eb0ad92299bba2a24ba86b8021c2b5d89c2531a918e913453e170dcfa125d1e Staging site: https://maven.apache.org/plugins-archives/maven-gpg-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven Assembly Plugin version 3.7.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.03.24 08:58, Slawomir Jaranowski wrote: Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12354406 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2073/ https://repository.apache.org/content/repositories/maven-2073/org/apache/maven/plugins/maven-assembly-plugin/3.7.1/maven-assembly-plugin-3.7.1-source-release.zip Source release checksum(s): maven-assembly-plugin-3.7.1-source-release.zip - SHA-512 : 599fb208058b2fea3ea6af6db6e56bd1d2653f8d36061c46c0fb0634f5e7b6fd7eb968fb05754538001ee692c21f4ae4289d040f74a9d327f1a4cd2eba38 Staging site: https://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven Compiler Plugin version 3.13.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.03.24 08:36, Slawomir Jaranowski wrote: Hi, We solved 10 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12354079 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCOMPILER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2072/ https://repository.apache.org/content/repositories/maven-2072/org/apache/maven/plugins/maven-compiler-plugin/3.13.0/maven-compiler-plugin-3.13.0-source-release.zip Source release checksum(s): maven-compiler-plugin-3.13.0-source-release.zip - SHA-512 : 99897c8350e50ba0ad9fcba210dad772d7f9e465358c35752942b71e3c7d2ca54d1e9115cc657130829135f1598a091436463744ef00de0cbee6042862abddf5 Staging site: https://maven.apache.org/plugins-archives/maven-compiler-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven Assembly Plugin version 3.7.0
Hi, +1 from me Kind regards Karl Heinz Marbaise On 07.03.24 19:27, Slawomir Jaranowski wrote: Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12353243 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2069/ https://repository.apache.org/content/repositories/maven-2069/org/apache/maven/plugins/maven-assembly-plugin/3.7.0/maven-assembly-plugin-3.7.0-source-release.zip Source release checksum(s): maven-assembly-plugin-3.7.0-source-release.zip - SHA-512 : fd25b79c126cf728fddc04f9f0cb56cbd5434d4f67001f88947ca677086a5d34e843154c6fe9dfb47ac85889ddd656a5df0ba3e1f6486e1a9d887fedf6d1200e Staging site: https://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven 4.0.0-alpha-13
Hi, +1 from me Kind regards Karl Heinz Marbaise On 06.03.24 21:42, Tamás Cservenák wrote: Howdy, This is a vote to release Apache Maven 4.0.0-alpha-13. We solved 32 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354062 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MNG/issues Release candidates: https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-13/ Staging repository: https://repository.apache.org/content/repositories/maven-2068/ Source release SHA512: - apache-maven-4.0.0-alpha-13-src.zip 5e997e382ad7e5021009b74a6a80b9c9076282a3a71260636efc99c28ffad2c4d093d896364e705d853015f6c7d949523fc78c4ebb6aa55edeb43e383f084e3d - apache-maven-4.0.0-alpha-13-src.tar.gz 59cc1b312b240e93e9f51ab9549c69385e12ccf5453b8e6238470437fce8ca802bda0eddc66ca94c5d6d05c02e44c0f78d0d7d2038998559a61df6e5c599da10 Staging site: https://maven.apache.org/ref/4-LATEST/ Note: site publishing (execution time of `mvn scm-publish:publish-scm`) now takes 32 minutes! We need to do something about this... 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 Apache Maven 4.0.0-alpha-13
Hi, I see the following with 4.0.0-alpha-13 with a test project (spring boot based 3.3.0-M2): [INFO] Unable to find the root directory. Create a .mvn directory in the root directory or add the root="true" attribute on the root project's model to identify it. [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for 'com.soebes.spring.example:employee:jar:0.0.1-SNAPSHOT' [WARNING] Ignored POM import for: org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.7.0@compile as already imported org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.10.2@compile. Add a the conflicting managed dependency directly to the dependencyManagement section of the POM. @ org.springframework.boot:spring-boot-dependencies:3.3.0-M2, /Users/khm/.m2/repository/org/springframework/boot/spring-boot-dependencies/3.3.0-M2/spring-boot-dependencies-3.3.0-M2.pom [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] The given bom file contains also a pluginManagement section with a number of plugins defined in The interesting part is that 4.0.0-alpha-12 does not produce such warning at all: [INFO] Unable to find the root directory. Create a .mvn directory in the root directory or add the root="true" attribute on the root project's model to identify it. [INFO] Scanning for projects... [INFO] [INFO] --< com.soebes.spring.example:employee >-- [INFO] Building Employee Demo Application 0.0.1-SNAPSHOT [INFO] from pom.xml [INFO] -[ jar ]-- [INFO] [INFO] --- clean:3.3.2:clean (default-clean) @ employee --- [INFO] Deleting /Users/khm/ws-git-soebes/examples/spring-boot-plus-spring-data/target [INFO] Any ideas what happens? Kind regards Karl Heinz Marbaise On 06.03.24 21:42, Tamás Cservenák wrote: Howdy, This is a vote to release Apache Maven 4.0.0-alpha-13. We solved 32 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354062 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MNG/issues Release candidates: https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-13/ Staging repository: https://repository.apache.org/content/repositories/maven-2068/ Source release SHA512: - apache-maven-4.0.0-alpha-13-src.zip 5e997e382ad7e5021009b74a6a80b9c9076282a3a71260636efc99c28ffad2c4d093d896364e705d853015f6c7d949523fc78c4ebb6aa55edeb43e383f084e3d - apache-maven-4.0.0-alpha-13-src.tar.gz 59cc1b312b240e93e9f51ab9549c69385e12ccf5453b8e6238470437fce8ca802bda0eddc66ca94c5d6d05c02e44c0f78d0d7d2038998559a61df6e5c599da10 Staging site: https://maven.apache.org/ref/4-LATEST/ Note: site publishing (execution time of `mvn scm-publish:publish-scm`) now takes 32 minutes! We need to do something about this... 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] Require Java 17 for Maven 4
Hi, +1 from me. Kind regards Karl Heinz Marbaise 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
Re: [VOTE] Require Java 17 for Maven 4
Hi, +1 from me. Kind regards Karl Heinz Marbaise 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 - 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
. JDK 21 will attract even more... latest technology? JDK 17 is not the latest... *Conclusion:* In conclusion, the proposal is to introduce LTS versions of Maven, namely Maven 3.10.x targeting Java 8 and Maven 4.0 targeting Java 17, presents a balanced approach to cater to the diverse needs of the Java development community. By providing stability, compatibility, and extended support for legacy projects with Maven 3.10.x, and enabling compatibility with the latest Java features and development practices with Maven 4.0, this versioning strategy ensures that both current and future projects can thrive within the Maven ecosystem. Please, maintain a constructive argument, since we need to move forward. Thank you! Best regards. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Shade Plugin version 3.5.2
Hi, +1 form my side. Kind regards Karl Heinz Marbaise On 17.02.24 19:00, Hervé Boutemy wrote: Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12352505=Text Staging repo: https://repository.apache.org/content/repositories/maven-2065/ https://repository.apache.org/content/repositories/maven-2065/org/apache/maven/plugins/maven-shade-plugin/3.5.2/maven-shade-plugin-3.5.2-source-release.zip Source release checksum(s): maven-shade-plugin-3.5.2-source-release.zip sha512: 23fcd21e6b915114efa133b1c4e46fa0b3d77874ff9d974e4bdb24940ea0ed9b7ffaf7f3d1e8a8549837cfe1de7ff2fc8ae7fc68bfc0477ea7a4b8b53e42f6f7% Staging site: https://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Plugin Tools version 3.11.0
+1 from me. Kind regards Karl Heinz Marbaise On 07.01.24 13:18, Michael Osipov wrote: Hi, we solved 10 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12353824 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2057/ https://repository.apache.org/content/repositories/maven-2057/org/apache/maven/plugin-tools/maven-plugin-tools/3.11.0/maven-plugin-tools-3.11.0-source-release.zip Source release checksum(s): maven-plugin-tools-3.11.0-source-release.zip sha512: 448dba8495c9f4859563cc418cb24113ec209119e8d53e82dae9c76f3c6fc917b14bac609e1978692eea5c88c3f89d60759c2193372e3d6c1bc640fb0afd7b6b Staging site: https://maven.apache.org/plugin-tools-archives/plugin-tools-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M10
+1 from me. Kind regards Karl Heinz Marbaise On 07.01.24 20:33, Michael Osipov wrote: Hi, IMPORTANT: This require the following staging repositories: * Maven Doxia 2.0.0-M9 we solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12354114 There is one issue left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-api Staging repo: https://repository.apache.org/content/repositories/maven-2058/ https://repository.apache.org/content/repositories/maven-2058/org/apache/maven/reporting/maven-reporting-api/4.0.0-M10/maven-reporting-api-4.0.0-M10-source-release.zip Source release checksum(s): maven-reporting-api-4.0.0-M10-source-release.zip sha512: 81258660b0598506f9b699f6364519045710f42bcebfe66a020e0b40e65677062deede88c9fe363201c03d72d159841e65d91789c24e7afc38b8e7d9482a1669 Staging site: https://maven.apache.org/shared-archives/maven-reporting-api-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 - 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.2
+1 from me. Kind regards Karl Heinz Marbaise 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 Surefire version 3.2.5
+1 from me. Kind regards Karl Heinz Marbaise On 06.01.24 21:05, Michael Osipov wrote: Hi, we solved 7 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12354100 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2055/ https://repository.apache.org/content/repositories/maven-2055/org/apache/maven/surefire/surefire/3.2.5/surefire-3.2.5-source-release.zip Source release checksum(s): surefire-3.2.5-source-release.zip sha512: 5c894574b5c13813e5cdfec20f47d92e632f625aa53a135d22477b996998119b0c4fbfcabd0bdd35aed20be2d6fa221310e28ce6be6967411f48a7c19aa52dde Staging site: https://maven.apache.org/surefire-archives/surefire-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: New year - new challenge - required Maven 3.6.3 as minimal for core Maven Plugins
On 05.01.24 17:02, Michael Osipov wrote: On 2024/01/05 15:52:54 Karl Heinz Marbaise wrote: ... On 05.01.24 16:19, Michael Osipov wrote: On 2024/01/05 14:37:44 Karl Heinz Marbaise wrote: +1 Also the point JDK11 (maybe even higher JDK17?) for Maven 4.0.0 as minimum runtime requirement.. This reminds me of https://github.com/openssl/openssl/issues/10902 and it provides very good reasons why not to do it. Maven is a low level tool -- as such it has to be available to as many devs as possible. Hm.. I have to admit that I don't see the relationship to OpenSSL and C++ compilers / Perl etc. and which reason do you have in mind? It is about replacing Perl with CMake. Perl has a much better availability than CMake... And where is the relationship to Maven? Apart from that Perl is not that available on a lot of systems (the last 10 years have changed that)... today Python is often more available than Perl... which would bring CMake back into the game... Furthermore not many people are building Curl from sources... I would say 99% of people consume them via their package manager (dnf, yum, apt etc.) of their distributions or via flatpak or alike...Who is building from source today? So I don't see here the in relationship to Maven... or are we talking about bootstrapping Maven from source without pre existing Maven/Ant etc. ? But for Maven 4. I see no problem in upgrading the minimum requirement to JDK 17 (runtime)... If people can not upgrade (for whatever reason) they can continue to use Maven 3.X ... Also as I mentioned several times before even with JDK 17 you can build code for java 7... and if that is not sufficient you can use Toolchain... (also mentioned several times before)... Apart from that if I take that argument in consequence (also mentioned several times before)... than we have to stop any upgrade in JDK minimum version and go back to JDK 1.5 or even 1.4 (or even less)...because there are people using those ancient versions... Please don't apply our possiblites to others and don't make any assumptions what others can or cannot do. Rasing to 17 w/o massively rewriting core to benefit from post-8 constructs a pure lie to ourselves. We cannot even keep JIRA issue count low. I'd really focus on what really matters. I have given solutions to solve possible issues... and now I should not show possible solutions... very interesting... Why is massively rewriting required? In Maven core (master branch) is already using a lot of JDK 8 parts.. which can be increased of course, for example using JDK17 as base line would make it possible to use sealed classes, records, var usage etc. only to mention a few... of course that will take time no doubt about that...(mentioned several times before)... Also staying on old things (JDK8 is old) will not attract new developers which is a thing in particular in relationship to the mentioned part about JIRA issues etc. meaning the number of contributors could be higher... Which is from my point of view exactly the opposite argument.. upgrade to most recent JDK 17 at min ... or even JDK 21... to get better attraction for other possible contributors.. https://www.jetbrains.com/lp/devecosystem-2023/java/ https://www.jetbrains.com/lp/devecosystem-2022/java/ https://www.jetbrains.com/lp/devecosystem-2021/java/ This represents nothing especially not those who aren't or cannot advertise what thy use. Never trust statistics you haven't falsified yourself. You should check the https://www.jetbrains.com/lp/devecosystem-2022/methodology/ etc. That's available for all given reports. You can get the raw data... > not those who aren't or cannot advertise what thy use. If they can not use more recent things they can continue to use Maven 3... (mentioned before).. that contradicts in itself.. described solutions which work and that should not be shown/mentioned...makes no sense. Those statistics mention things like usage of JDK 7, 6 and even 5. What is the problem here? Only those reports show that the number of the usage for JDK5,6,7 is very low...not to say extremely low... Based on which argument do you conclude that we can not to upgrade to JDK 17 or even to JDK 21: for Maven 4? 1. It needs time to change things in core 2. We would exclude people (discussion about how many?) who can not upgrade. Answers to them: 1. It has taken time to incorporate changes for JDK 8 in core and plugins etc.. and it will take time to change more of course.. no doubt about that. 2. Mentioned solutions for that. (continue to use Maven 3.X; Toolchain). Are those things a reason not to lift ? No. Furthermore So that means your own arguments are now contradicted... Many other tools and libraries and frameworks already did that (Spring Boot 3(JDK 17), Quarkus(JDK 17), Micronaut (JDK 17) etc., . and even Jakarta EE 11 has set even JDK 21 as baseline... (https://jakarta.ee/specifications/platform/11/) Kind regards Karl Heinz Marbaise
Re: New year - new challenge - required Maven 3.6.3 as minimal for core Maven Plugins
... On 05.01.24 16:19, Michael Osipov wrote: On 2024/01/05 14:37:44 Karl Heinz Marbaise wrote: +1 Also the point JDK11 (maybe even higher JDK17?) for Maven 4.0.0 as minimum runtime requirement.. This reminds me of https://github.com/openssl/openssl/issues/10902 and it provides very good reasons why not to do it. Maven is a low level tool -- as such it has to be available to as many devs as possible. Hm.. I have to admit that I don't see the relationship to OpenSSL and C++ compilers / Perl etc. and which reason do you have in mind? But for Maven 4. I see no problem in upgrading the minimum requirement to JDK 17 (runtime)... If people can not upgrade (for whatever reason) they can continue to use Maven 3.X ... Also as I mentioned several times before even with JDK 17 you can build code for java 7... and if that is not sufficient you can use Toolchain... (also mentioned several times before)... Apart from that if I take that argument in consequence (also mentioned several times before)... than we have to stop any upgrade in JDK minimum version and go back to JDK 1.5 or even 1.4 (or even less)...because there are people using those ancient versions... https://www.jetbrains.com/lp/devecosystem-2023/java/ https://www.jetbrains.com/lp/devecosystem-2022/java/ https://www.jetbrains.com/lp/devecosystem-2021/java/ Kind regards Karl Heinz Marbaise M - 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: New year - new challenge - required Maven 3.6.3 as minimal for core Maven Plugins
Hi, I'm the same opinion to upgrade to the most recent Maven 3.X version.. for the plugins... +1 (but I'm ok also to use Maven 3.6.3 as minimum).. +1 Also the point JDK11 (maybe even higher JDK17?) for Maven 4.0.0 as minimum runtime requirement.. Kind regards Karl Heinz Marbaise On 31.12.23 00:54, Tamás Cservenák wrote: +1 to Jorge. As I understand it, this is the "minimal version supported" (prerequisite) we talk about here. But imo 3.x plugins should compile against lastest 3.x Maven. T On Sun, Dec 31, 2023, 00:35 Jorge Solórzano wrote: I know that a build tool is different from a framework, but we are again missing the point here, is not about framework vs build tools, the point is that newer projects already require new Java versions, and if legacy projects require using an old Java version, then those projects will still be using Maven 3.x anyway and that is perfectly fine. What should be the threshold to move to a newer Java version? (I'm talking about using Java 11 on Maven 4.0, not on 3.x). Sorry I didn't want to hijack this thread for the Java version discussion, yet I wish to know what is the benefit of "supporting" plugins on older versions of Maven, I'm asking as a user since I'm not a Maven core developer, PMC,r committer, just an occasional contributor, and again, I might be missing something, but what is the benefit of updating plugins on a project and using an older version of Maven? As a user is weird to me that Maven versions prior 3.8.x are EOL, yet plugins provide Maven API compatibility down to 3.2.5. It seems that is indeed a new challenge to require Maven 3.6.3 as minimal for core plugins ;) Regards and Happy New Year! On Sat, Dec 30, 2023 at 6:30 PM Michael Osipov wrote: Am 2023-12-30 um 16:43 schrieb Jorge Solórzano: I'm a bit confused here, why would anyone update Maven plugins in a project and NOT update Maven Core? Older versions of Maven are EOL, is expected that Maven Core is backward-compatible on minor releases so updating Maven Core should be straightforward. I might be missing something but I don't see a scenario where someone updates plugins but does not update Maven itself, I would expect the opposite, it should be more common to update Maven core than plugins (although that is just my perception). The question remains: Why should we use 3.5.4 instead of 3.6.3 as a minimum in plugins? don't get me wrong, I don't mind if we use 3.5.4 instead of 3.6.3 if the maintenance/support is the same, but knowing that CI uses Maven 3.6.3 and newer, and without knowing why plugins should be supported on 3.5.4, my vote will go to use 3.6.3. This discussion reminds me of the minimum required Java version, there was even an informal poll <https://twitter.com/khmarbaise/status/1549429653202518016> with more than 80% asking for newer Java releases, and I would love to see Maven 4.0 require at least Java 11, but here we are, one year later and still on Java 8 because some prefer to be working with Java 7 or even Java 6. The ecosystem is moving forward, SpringBoot, Quarkus, Jakarta EE, and some dependencies are slowly moving to at least Java 11, if a project requires Java 8 (for whatever reason), then it will remain on Maven 3.x, moving to Java 11 is conservative enough for Maven 4.0. Those who are working with JDK less than 8 are already a minority... https://www.jetbrains.com/lp/devecosystem-2023/java/ Also the usage of JDK 17 is increasing... I expect that JDK21 will increase over this year... You are confusing a low-level tool which should be accessible to everyone compared to a specific framework. Regarding Spring Boot: I consider that a total dick move dropping javax namespace support for a huge user base. Regardless of the Java version. M - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire version 3.2.4
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 01.01.24 12:19, Michael Osipov wrote: Hi, we solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12354030 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2054/ https://repository.apache.org/content/repositories/maven-2054/org/apache/maven/surefire/surefire/3.2.4/surefire-3.2.4-source-release.zip Source release checksum(s): surefire-3.2.4-source-release.zip sha512: a18858d35b07483d7d175d161d022366eb1861541ed82c498d6860cff8e34552a42c37b3909cfebc620b949dfa2095571d324079e5bde03ec2c0839c164328e3 Staging site: https://maven.apache.org/surefire-archives/surefire-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Compiler Plugin version 3.12.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 21.12.23 08:54, Slawomir Jaranowski wrote: Hi, We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12354061 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCOMPILER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2051/ https://repository.apache.org/content/repositories/maven-2051/org/apache/maven/plugins/maven-compiler-plugin/3.12.1/maven-compiler-plugin-3.12.1-source-release.zip Source release checksum(s): maven-compiler-plugin-3.12.1-source-release.zip - SHA-512 : 8aba1fcb580110119422b5e323d36af6179fcefc485d3354189cfecad987825ca168a61687d52c2a6561559d14387946f6f46606649cc3980cb67136d7dbc8eb Staging site: https://maven.apache.org/plugins-archives/maven-compiler-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven Compiler Plugin version 3.12.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.12.23 22:04, Slawomir Jaranowski wrote: Hi, We solved 22 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12353748 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCOMPILER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-2049/ https://repository.apache.org/content/repositories/maven-2049/org/apache/maven/plugins/maven-compiler-plugin/3.12.0/maven-compiler-plugin-3.12.0-source-release.zip Source release checksum(s): maven-compiler-plugin-3.12.0-source-release.zip - SHA-512 : 026e4affea10983e11c0b951ecc75b45deae32b9938d03f962174416f79c0bf75f31985e7add2e5312ae1d2c6a9b26f1f7bb54da7a214a0c3db275e0f41bf572 Staging site: https://maven.apache.org/plugins-archives/maven-compiler-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven 4.0.0-alpha-10
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 18.12.23 19:16, Guillaume Nodet wrote: I'm starting a new vote to release this new alpha. This mainly brings in latest resolver alpha release which fixes a nasty bug causing maven to never quit. Fwiw, a few plugins have already been ported to the new API (clean, install, deploy, resources, compiler) and do pass their integration tests, i'll update the PR https://github.com/apache/maven/pull/1048/files asap. 13 issues solved: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354013 Staging repository: https://repository.apache.org/content/repositories/maven-2050 Dev dist directory: https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-10/ Staged site: https://maven.apache.org/ref/4-LATEST/ 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] Release Apache Maven 4.0.0-alpha-9
Hi, +1 from me. Currently testing with more projects... some issues found which I will document via JIRA...nothing which blocks the current release... Kind regards Karl Heinz Marbaise On 08.12.23 20:12, Guillaume Nodet wrote: I'm starting a new vote to release this new alpha. This alpha release provides a bunch of new things: * switch to maven-resolver 2.0.0-alpha-3 * multi-threaded model builder * namespace support in xml configuration * ability to create proxies to inject SessionScoped beans into singletons * Maven 4 API improvements: plugin api, dependency collection / resolution, version / version range resolution Fwiw, a few plugins have already been ported to the new API (clean, install, deploy, resources, compiler) and do pass their integration tests, i'll update the PR https://github.com/apache/maven/pull/1048/files asap. 29 issues solved: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353746 Staging repository: https://repository.apache.org/content/repositories/maven-2042 Dev dist directory: https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-9/ Staged site: https://maven.apache.org/ref/4-LATEST/ Draft for release notes: https://github.com/apache/maven-site/pull/474 https://github.com/apache/maven-site/blob/434a9bad8c13b6df76643d4d2ef0628b5ff4a8d4/content/markdown/docs/4.0.0-alpha-9/release-notes.md 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] Release Maven Surefire version 3.2.3
+1 from me. Kind regards Karl Heinz Marbaise On 09.12.23 21:53, Michael Osipov wrote: Hi, we solved 7 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12353823 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-2043/ https://repository.apache.org/content/repositories/maven-2043/org/apache/maven/surefire/surefire/3.2.3/surefire-3.2.3-source-release.zip Source release checksum(s): surefire-3.2.3-source-release.zip sha512: 024ebecddfebd05af7fb1c812333930b9277a321882a52cdd41758d45a6af3e0f1b1dc5e8f7d14acf4e593046e74750cab154cac7eb658d89bf8198a11b72369 Staging site: https://maven.apache.org/surefire-archives/surefire-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver 2.0.0-alpha-3
Hi, +1 from me Kind regards Karl Heinz Marbaise On 28.11.23 15:59, Tamás Cservenák wrote: Howdy, Note: This is a third (and hopefully last, unless something unexpected crops out) preview release of Resolver 2.0.0, that would allow any downstream consumers to try it out and adapt. It contains major cleanup and package and class renames (not affecting public APIs, but affecting configuration!). It also includes "windows fix" from the 1.9.18 version. For configuration changes, see https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html Note: this page above is from now on GENERATED out of sources. Before it was manually authored that was error prone and laborious, plus there was a source vs page discrepancy as well it omitted some properties (usually by mistake). IF the vote is successful, the staging site will NOT be moved to https://maven.apache.org/resolver/ but instead will be made reachable from https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-3/ only. The 1.9.18 is still the "latest stable" release of Maven Resolver. === We solved 12 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353963 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues Staging repository: https://repository.apache.org/content/repositories/maven-2040 Source release SHA512: 3eeb611f90da03a20479ef6086a3112ffd5c0289a72011e65c274e919ac2573d5d3fa124c1a3e506fdbecb15b22969c925ae1c1937b0e0778ceeb8fe8803dead Staging site: https://maven.apache.org/resolver-archives/resolver-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] Apache Maven Build Cache Extension 1.1.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 27.11.23 03:12, Olivier Lamy wrote: Hi, I'd like to release the Apache Maven Build Cache Extension 1.1.0. We've fixed 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352470=Text=12324820 Staging repo https://repository.apache.org/content/repositories/maven-2038/ source release https://repository.apache.org/content/repositories/maven-2038/org/apache/maven/extensions/maven-build-cache-extension/1.1.0/maven-build-cache-extension-1.1.0-source-release.zip sha512 https://repository.apache.org/content/repositories/maven-2038/org/apache/maven/extensions/maven-build-cache-extension/1.1.0/maven-build-cache-extension-1.1.0-source-release.zip.sha512 Staging site: https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/ Vote open for 72h +1 0 -1 regards Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.9.6
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 28.11.23 11:23, Tamás Cservenák wrote: Howdy, Note: This release improves Windows experience (via use of Resolver 1.9.18) and makes possible using newer bytecode as Maven components (by upping Sisu) and adds ability to exclude plugins from validation. --- We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353686 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-2039 Dev dist directory (binary bundles updated): https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.6/ Source release checksums: apache-maven-3.9.6-src.tar.gz.sha512 c14b97703082af495225cec652ad1ec58cbcd069040cdfa16a7b9270058574c73524ce15217e83153fe23b2449ef1afd73a4ef42bd05abd3cfdfadfc3da7f7bf apache-maven-3.9.6-src.zip.sha512 e1773ea34a90a16a4ba68bd0304fe73b34fbc2d02f74c195aaa610a959ccd9ce500194b72dc957a2b8af2af28c63e342f7f98fcd4e5b795a0af8364e5fb72bcf Staged site: https://maven.apache.org/ref/3-LATEST/ Draft for release notes: https://github.com/apache/maven-site/pull/469 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] Release Apache Maven Doxia Sitetools version 2.0.0-M16
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 18.11.23 10:23, Michael Osipov wrote: Hi, we solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12353864 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open Staging repo: https://repository.apache.org/content/repositories/maven-2033 https://repository.apache.org/content/repositories/maven-2033/org/apache/maven/doxia/doxia-sitetools/2.0.0-M16/doxia-sitetools-2.0.0-M16-source-release.zip Source release checksum(s): doxia-sitetools-2.0.0-M16-source-release.zip sha512: 8a17c9c12e14c68e3a6fb5cf5f76b25fc980ed9680bfda1c031244e2f8de274d78468619ae381017f28e3775aa0d14f6912e90242013bc397feedeabe6d34ca1 Staging site: https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Project Info Reports Plugin version 3.5.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 17.11.23 22:54, Michael Osipov wrote: Hi, we solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12353875 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPIR/issues Staging repo: https://repository.apache.org/content/repositories/maven-2031/ https://repository.apache.org/content/repositories/maven-2031/org/apache/maven/plugins/maven-project-info-reports-plugin/3.5.0/maven-project-info-reports-plugin-3.5.0-source-release.zip Source release checksum(s): maven-project-info-reports-plugin-3.5.0-source-release.zip sha512: c5c9feedceacccfeec06bb503ec9e80f08a88671892cf260a0385cbde84f2bee3e283c8e62b3c1d20cf847af0e81033c618cf4fe6dbc20f2b56050331fb8a2d4 Staging site: https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver 1.9.17
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 18.11.23 00:27, Tamás Cservenák wrote: Howdy, Note: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode. We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353659 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues Staging repository: https://repository.apache.org/content/repositories/maven-2032/ Source release SHA512: c594df21e82b198abefb1fdad67d68c1c6eda69e279ebb9bd1e1c20e361ae40f4bab99dfc00f9699e9129760a864b703ced61322361debe3abeefafcd78f3633 Staging site: https://maven.apache.org/resolver-archives/resolver-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: Changing Minimum Build Requirements for plugins to JDK11
Hi,
On 14.11.23 14:16, Hervé Boutemy wrote:
no need to change the build prerequisite: just add a profile to activate the
release flag on newer JDK:
https://issues.apache.org/jira/browse/MPOM-447
Add another profile...
it would be better to clean up those things and make clean upgrade
way...instead ...
Kind regards
Karl Heinz Marbaise
Regards,
Hervé
Le lundi 13 novembre 2023, 20:38:00 CET Karl Heinz Marbaise a écrit :
Hi,
currently we have already the build requirements for Maven Core at JDK11+
So in consequence I would suggest to lift the minimum requirement for
building plugins to JDK11.
That means also we can use "--release 8" option
(8) instead of
source/target which is not correct based on the warnings we get like:
"[WARNING] bootstrap class path not set in conjunction with -source 8"
which we get in all plugins based on the configuration in maven parent
using this:
8
1.${javaVersion}
1.${javaVersion}
which is not correct because we don't use animalsniffer anymore.
So my suggestion is to lift the JDK build requirements to JDK11...
and use the 8 which
will prevent the warning. Also brings us back the safety net which
animal-sniffer was before.
Later on version of maven-parent (v42?) should change the whole
configuration (there are some related parts like maven-pmd-plugin,
maven-enforcer-plugin (enforce-byte-code max)..also toolchain-plugin...
Furthermore we could get rid of the profile for JDK11+ related to
spotless-maven-plugin ...
Based on the upgrade to maven-parent v41 we could also enhance the build
pipelines to build on JDK21
WDYT?
Kind regards
Karl Heinz Marbaise
-
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: Changing Minimum Build Requirements for plugins to JDK11
Hi,
On 14.11.23 12:54, Elliotte Rusty Harold wrote:
I'm OK with Java 11 required to build Maven in 2023, but I'll play my
broken record: it is not yet OK to require Java 11 to run Maven or
plugins.
There are still a lot of developers out there who are using JDK 8
toolchains. and contrary to common claims, it is still a supported
version by many JDK vendors.
For runtime:
Based on that argument we can are trapped in eternity ... because
supporting contracts can go to 2035+ etc.
If someone needs to support JDK 8; toolchain is the right way to go if
it is really required... Most of the time JDK11, 17 or even 21 using
--release 8 will be sufficient..
Buildtime is only for committers and contributors which from my
perspective is a plus...
Apart from that we already require JDK11+ for Core and resolver ...
Kind regards
Karl Heinz Marbaise
On Mon, Nov 13, 2023 at 2:38 PM Karl Heinz Marbaise wrote:
Hi,
currently we have already the build requirements for Maven Core at JDK11+
So in consequence I would suggest to lift the minimum requirement for
building plugins to JDK11.
That means also we can use "--release 8" option
(8) instead of
source/target which is not correct based on the warnings we get like:
"[WARNING] bootstrap class path not set in conjunction with -source 8"
which we get in all plugins based on the configuration in maven parent
using this:
8
1.${javaVersion}
1.${javaVersion}
which is not correct because we don't use animalsniffer anymore.
So my suggestion is to lift the JDK build requirements to JDK11...
and use the 8 which
will prevent the warning. Also brings us back the safety net which
animal-sniffer was before.
Later on version of maven-parent (v42?) should change the whole
configuration (there are some related parts like maven-pmd-plugin,
maven-enforcer-plugin (enforce-byte-code max)..also toolchain-plugin...
Furthermore we could get rid of the profile for JDK11+ related to
spotless-maven-plugin ...
Based on the upgrade to maven-parent v41 we could also enhance the build
pipelines to build on JDK21
WDYT?
Kind regards
Karl Heinz Marbaise
-
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
Changing Minimum Build Requirements for plugins to JDK11
Hi,
currently we have already the build requirements for Maven Core at JDK11+
So in consequence I would suggest to lift the minimum requirement for
building plugins to JDK11.
That means also we can use "--release 8" option
(8) instead of
source/target which is not correct based on the warnings we get like:
"[WARNING] bootstrap class path not set in conjunction with -source 8"
which we get in all plugins based on the configuration in maven parent
using this:
8
1.${javaVersion}
1.${javaVersion}
which is not correct because we don't use animalsniffer anymore.
So my suggestion is to lift the JDK build requirements to JDK11...
and use the 8 which
will prevent the warning. Also brings us back the safety net which
animal-sniffer was before.
Later on version of maven-parent (v42?) should change the whole
configuration (there are some related parts like maven-pmd-plugin,
maven-enforcer-plugin (enforce-byte-code max)..also toolchain-plugin...
Furthermore we could get rid of the profile for JDK11+ related to
spotless-maven-plugin ...
Based on the upgrade to maven-parent v41 we could also enhance the build
pipelines to build on JDK21
WDYT?
Kind regards
Karl Heinz Marbaise
-
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.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 25.10.23 17:23, Tamás Cservenák wrote: Howdy, We solved 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12353767 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MINDEXER/issues Staging repository: https://repository.apache.org/content/repositories/maven-2018 Source release SHA512: 249cab0df95433455540e13298d074a8d45d543a355f64b5e86268831ee65e226c8d24c7ba270973ee3bca68c842d23641236e3b1bcb237fe4c9d869393d5e69 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.0
Hi, +1 from me. Kind regards Karl Heinz marbaise On 25.10.23 17:23, Tamás Cservenák wrote: Howdy, We solved 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12353767 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MINDEXER/issues Staging repository: https://repository.apache.org/content/repositories/maven-2018 Source release SHA512: 249cab0df95433455540e13298d074a8d45d543a355f64b5e86268831ee65e226c8d24c7ba270973ee3bca68c842d23641236e3b1bcb237fe4c9d869393d5e69 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] Retire Maven Docck Plugin
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 17.10.23 00:50, Slawomir Jaranowski wrote: Hi, - Last release was in 2015 - use Maven 2.2.1 - we have a Maven Plugin Tools - which should be one project for build and check Maven plugins - no active development ... https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDOCCK%20AND%20(%20resolution%20%3D%20Unresolved%20OR%20fixVersion%20%3D%203.0.0) - no working with current plugins I therefore propose that we retire maven-docck-plugin - https://maven.apache.org/plugins/maven-docck-plugin/ If this vote is successful I will make one final release of the plugin, making it clear on the plugin site that it has been retired. After that the source code will be moved into read-only mode. The process for retiring a plugin is described here: https://maven.apache.org/developers/retirement-plan-plugins.html The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... [1] - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.9.5
Hi,
the permissions in the .tar.gz archive are Ok now.
Please update the SHA512 because it's the previous one..(I've checked
the .tar.gz) but I assume that the SHA512 for the -bin.zip has changed
also)...
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.5/binaries/
Kind regards
Karl Heinz Marbaise
On 02.10.23 11:10, Tamás Cservenák wrote:
Bah,
This is the same problem as before... but originally it happened on my
desktop. This time the release was done from my laptop :(
I believe the fix is the same as before: I should rebuild from the tag,
after I fixed my local repository, as source bundles we vote on are
unchanged...
T
On Mon, Oct 2, 2023 at 9:14 AM Herve Boutemy wrote:
thinking twice, I need to change to -1: this may impact users that expect
to use the group permissions to use Maven binaries
sorry
I don't know what tests you are doing with permissions on your
environment, but these tests leak releases :(
Regards,
Hervé
On 2023/10/02 07:11:02 Herve Boutemy wrote:
+1
but Reproducible not fully ok: reference build done with JDK 17 on *nix
and umask 022
apache-maven-3.9.5-bin.zip and .tar.gz suffer from weird umask (go-r) on
wagon jars:
$ diffoscope
target/reference/org.apache.maven/apache-maven-3.9.5-bin.zip
apache-maven/target/apache-maven-3.9.5-bin.zip
--- target/reference/org.apache.maven/apache-maven-3.9.5-bin.zip
+++ apache-maven/target/apache-maven-3.9.5-bin.zip
│┄ Archive contents identical but files differ, possibly due to
different compression levels. Falling back to binary comparison.
├── zipinfo {}
│ @@ -81,21 +81,21 @@
│ -rw-r--r-- 2.0 unx74345 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-resolver-provider-3.9.5.jar
│ -rw-r--r-- 2.0 unx 317619 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-resolver-impl-1.9.16.jar
│ -rw-r--r-- 2.0 unx37757 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-resolver-named-locks-1.9.16.jar
│ -rw-r--r-- 2.0 unx51503 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-resolver-spi-1.9.16.jar
│ -rw-r--r-- 2.0 unx 379348 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/org.eclipse.sisu.inject-0.3.5.jar
│ -rw-r--r-- 2.0 unx 4225 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/plexus-component-annotations-2.1.0.jar
│ -rw-r--r-- 2.0 unx 289577 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-compat-3.9.5.jar
│ --rw--- 2.0 unx55101 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/wagon-provider-api-3.5.3.jar
│ +-rw-r--r-- 2.0 unx55101 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/wagon-provider-api-3.5.3.jar
│ -rw-r--r-- 2.0 unx 205307 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/org.eclipse.sisu.plexus-0.3.5.jar
│ -rw-r--r-- 2.0 unx58284 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/commons-cli-1.5.0.jar
│ --rw--- 2.0 unx 9405 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/wagon-http-3.5.3.jar
│ --rw--- 2.0 unx40832 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/wagon-http-shared-3.5.3.jar
│ --rw--- 2.0 unx 785639 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/httpclient-4.5.14.jar
│ --rw--- 2.0 unx11350 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/wagon-file-3.5.3.jar
│ +-rw-r--r-- 2.0 unx 9405 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/wagon-http-3.5.3.jar
│ +-rw-r--r-- 2.0 unx40832 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/wagon-http-shared-3.5.3.jar
│ +-rw-r--r-- 2.0 unx 785639 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/httpclient-4.5.14.jar
│ +-rw-r--r-- 2.0 unx11350 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/wagon-file-3.5.3.jar
│ -rw-r--r-- 2.0 unx16555 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/jcl-over-slf4j-1.7.36.jar
│ -rw-r--r-- 2.0 unx40277 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-resolver-connector-basic-1.9.16.jar
│ -rw-r--r-- 2.0 unx16249 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-resolver-transport-file-1.9.16.jar
│ -rw-r--r-- 2.0 unx55689 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-resolver-transport-http-1.9.16.jar
│ -rw-r--r-- 2.0 unx 327891 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/httpcore-4.4.16.jar
│ -rw-r--r-- 2.0 unx 360738 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/commons-codec-1.16.0.jar
│ -rw-r--r-- 2.0 unx32488 b- defN 23-Oct-01 18:38
apache-maven-3.9.5/lib/maven-resolver-transport-wagon-1.9.16.jar
│ --- target/reference/org.apache.maven/apache-maven-3.9.5-bin.zip
Regards,
Hervé
On 2023/10/01 19:07:05 Tamás Cservenák wrote:
Howdy,
Note: This release completes the main goals of Maven 3.9.x lineage,
among
others moving to Java 8 and transition to latest Resolver 1.9.x
features
(new robust transports, local repository locking, provided checksums,
remote repository filtering and more). Maven Resolver 1.9.x lineage is
already in "bugfix only" (no new features) maintenance mode, and this
makes
Maven 3.9
Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M10
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 01.10.23 20:19, Michael Osipov wrote: Hi, IMPORTANT: Requires Doxia Sitetools 2.0.0-M12 vote/staging repo! we solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353492 There are no issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl Staging repo: https://repository.apache.org/content/repositories/maven-1994/ https://repository.apache.org/content/repositories/maven-1994/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M10/maven-reporting-impl-4.0.0-M10-source-release.zip Source release checksum(s): maven-reporting-impl-4.0.0-M10-source-release.zip sha512: 1e51d44a8047dec49e9f2087a92dc86cb86413a78bc3a1f3324ba89e3f76c044c591ec5df688cc37b7535aa91ab532b32ecf990aae9bd0b9020b00e74847a417 Staging site: https://maven.apache.org/shared-archives/maven-reporting-impl-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M12
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 01.10.23 20:03, Michael Osipov wrote: Hi, we solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12353413 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open Staging repo: https://repository.apache.org/content/repositories/maven-1993 https://repository.apache.org/content/repositories/maven-1993/org/apache/maven/doxia/doxia-sitetools/2.0.0-M12/doxia-sitetools-2.0.0-M12-source-release.zip Source release checksum(s): doxia-sitetools-2.0.0-M12-source-release.zip sha512: f78a743d75fd551a8fdc1e80050d2f2fdb68c3e43840524bb94cb9ab3a5c98f3322d143883e42f25dd61cb112425114ec0e39b4a18a87208cad3832f5af9 Staging site: https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. IMPORTANT: This is expected to be the last milestone before 2.0.0 GA. [ ] +1 [ ] +0 [ ] -1 - 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: [VOTE] Release Apache Maven 3.9.5
Hi, +1 from me... with the exceptions as Hervé mentioned (permissions on the wagon jars and httpclient jar)... and the points Gary mentioned. Kind regards Karl Heinz Marbaise On 01.10.23 21:07, Tamás Cservenák wrote: Howdy, Note: This release completes the main goals of Maven 3.9.x lineage, among others moving to Java 8 and transition to latest Resolver 1.9.x features (new robust transports, local repository locking, provided checksums, remote repository filtering and more). Maven Resolver 1.9.x lineage is already in "bugfix only" (no new features) maintenance mode, and this makes Maven 3.9.x lineage getting into this maintenance mode as well. I do foresee some more Maven 3.9.x releases with usual fluff (bug fixes, lifecycle plugin updates), but the focus should move to upcoming Maven 4, Resolver 2 and mvnd (at least when "core" is considered). --- We solved 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353460 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-1995 Dev dist directory (binary bundles updated): https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.5/ Source release checksums: apache-maven-3.9.5-src.zip sha512: f1e7f36a6423c4f6d98e599120ede3a9f9f62448edeb2d49ffbdc05e36548190049bc83aae4f49e3305da1060d7b8e49477a55cb78b938951fd41ab3d360995f apache-maven-3.9.5-src.tar.gz sha512: fd8f9c4f3c6af001d11146102ba491b248163cd45d8be16907f7dcdc763eef4a081a02286b28a74de7f48c3f377a0a4491d2fa9155c906466aa3c831a5b4ef8e Staged site: https://maven.apache.org/ref/3-LATEST/ Draft for release notes: https://github.com/apache/maven-site/pull/458 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] Release Apache Maven Shade Plugin version 3.5.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 21.09.23 21:51, Slawomir Jaranowski wrote: Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12353341 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1990/ https://repository.apache.org/content/repositories/maven-1990/org/apache/maven/plugins/maven-shade-plugin/3.5.1/maven-shade-plugin-3.5.1-source-release.zip Source release checksum(s): maven-shade-plugin-3.5.1-source-release.zip - SHA-512 : 02a72361203356dfccd4a4dca9459e9ef9e7b7e3852500633de920200c3525ef28bdf5e585791105dbf62ab61050c65300fc1d58495983307ddb58e9562e58c8 Staging site: https://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Apache Maven Javadoc Plugin version 3.6.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 12.09.23 08:22, Henning Schmiedehausen wrote: Hi, We solved 16 issues:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12352956 There are still a couple of issues left in JIRA:https://issues.apache.org/jira/projects/MJAVADOC?filter=allopenissues Staging repo:https://repository.apache.org/content/repositories/maven-1989/https://repository.apache.org/service/local/repositories/maven-1989/content/org/apache/maven/plugins/maven-javadoc-plugin/3.6.0/maven-javadoc-plugin-3.6.0-source-release.zip Source release checksum(s): maven-javadoc-plugin-3.6.0-source-release.zip sha512: 82fa3e3685b90225749ae884fd9ea2cb72385524e76df299c5176baed983f39a433fa29e93554e207d8ed9aaa10bb6e7b148409a865ecce1b3f40ef0cf9032d4 Staging site:https://maven.apache.org/plugins-archives/maven-javadoc-plugin-LATEST/ Guide to testing staged releases:https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 Resolver 1.9.15
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 04.08.23 14:45, Tamás Cservenák wrote: Howdy, Context: This release focuses on "third party integrations" and provides a migration path for those who rely on deprecated `ServiceLocator`, which is about to be dropped in the near future (planned for 2.0.0). The main focus is on new supplier artifact: https://repository.apache.org/content/repositories/maven-1984/org/apache/maven/resolver/maven-resolver-supplier/1.9.15/ The new module is described here: https://maven.apache.org/resolver-archives/resolver-LATEST/third-party-integrations.html === We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353445 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues Staging repository: https://repository.apache.org/content/repositories/maven-1984 Source release SHA512: 94567525457ce734252686f24b8c422b2808dd9ff65763b09da7a92214e1292c0b6458619cbd8a1e73047bb1e93cab3b035fcf8062725e6c37566dc6aed68994 Staging site: https://maven.apache.org/resolver-archives/resolver-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 Apache Maven 3.9.4 -- take two
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 31.07.23 12:29, Tamás Cservenák wrote: Howdy, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353369 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 (NEW, old was maven-1982): https://repository.apache.org/content/repositories/maven-1983 Dev dist directory (binary bundles updated): https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.4/ Source release checksums: apache-maven-3.9.4-src.zip sha512 (UNCHANGED): 7a45cfd1f50e51246bbbeef769bf0c61ec08320ac260eed6b54ffce060a3186c99e902b3407ed9aa98fe02ad9b618b1bd2741275c05c7cdac24f0bc799d324e0 apache-maven-3.9.4-src.tar.gz sha512 (UNCHANGED): 7a77f7e19c5165be8dd886ae06a52c6d6a94b1419917d2e035e937114c7cff5aea19d8ea3614485c1876185e70f4fbdd80b673f56f7d344fae75e51d62f3100c Binary release checksums: apache-maven-3.9.4-bin.tar.gz - SHA-512 : deaa39e16b2cf20f8cd7d232a1306344f04020e1f0fb28d35492606f647a60fe729cc40d3cba33e093a17aed41bd161fe1240556d0f1b80e773abd408686217e apache-maven-3.9.4-bin.zip - SHA-512 : 755e7b757ea011621d704b9d2bee8fc344b77c13117077caa71abea560f20926a2bc8c96f990ed298f2dfc14bdba376566ee11c66c547f2594579f9cb3c50e1c Staged site: https://maven.apache.org/ref/3-LATEST/ Draft for release notes: https://github.com/apache/maven-site/pull/442 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: Possible improvements on Maven
Hi, On 28.06.23 12:55, #ZHAO LIDA# wrote: Dear Maven maintainers, we are studying Maven dependency specifications and we would like to offer several possible improvements for Maven. (1) The scope management of Maven is complicated and hard to distinguish. Maven maintained 6 scopes (i.e., compile, runtime, provided, system, test, and import). As already mentioned system-scope is deprecated for a long time.. Compare to newer package managers such as NPM, which only has two scopes (i.e., dependencies, devdependencies), others have already mentioned that it has more of them. Maven has too many types of scopes, which makes it more difficult for users to understand. Some people say even it has not enough of them. Having a more fine grained control.. We went over all POMs on the Maven Central (around 8M artifacts, collected in March 2022) and count the frequency of all types of scope. Some of the scopes are rarely used. Only 0.35% of POMs in the Maven Center used system scope. That's really good...this can only be very old artifacts. Also, system scope is similar to provided scope, and import scope can hardly be regarded as a dependency scope. provided is completely different to provided.. We suggest simplifying the types of scopes by merging system into provided and removing import. theoretically we could do something like that, but unfortunately we can not break all 8 M artifacts... (2) In the documentation of Default Artifact Handlers (https://maven.apache.org/ref/3.9.3/maven-core/artifact-handlers.html), > type and classifier should introduce more commonly used values as their default value to provide better examples. >We found that the default values are rarely used and are not good examples for > users to understand the use of the settings. Setting commonly used values as default can help users understand the usage of the settings. We went over all POMs on the Maven Central (around 8M artifacts, collected in March 2022) and count the frequency of all possible values of classifier and type. According to our research, in classifier, the default values have low frequencies, including tests (1.05%), > javadoc (0.35%), sources (0.29%) looks a bit strange because all artifacts which will be uploaded to central have to have sources/javadoc ... have you checked the pom files or the artifacts in central? Often generation of sources/javadoc or alike a done via profiles in pom files... Means have you used search.maven.org ? and client(0.01%). More commonly used values are features (1.20%), linux-x86_64 (0.34%), and osx-x86_64 (0.27%). Could be dependent on OSGi packages... As for type, the top default values are pom (4.38%), test-jar (2.85%), war (1.08%) and the rest of the values are all below 0.1%. Other common examples are esa (2.53%), zip (1.88%), and xml (1.31%). Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [RESULT] [VOTE] Release Apache Maven 3.9.3
Hi, On 26.06.23 15:48, Karl Heinz Marbaise wrote: Hi, On 26.06.23 12:53, Tamás Cservenák wrote: Howdy, The vote has passed with the following result: +1b: Romain, Henning, Karl Heinz Missing: * Slawomir Jaranowski * Tamás Cservanák and also missed: * Guillaume Nodet Kind regards Karl Heinz Also please CC post on private pmc list. Kind regards Karl Heinz +2nb: Delany PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release to the board report. Thanks T - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [RESULT] [VOTE] Release Apache Maven 3.9.3
Hi, On 26.06.23 12:53, Tamás Cservenák wrote: Howdy, The vote has passed with the following result: +1b: Romain, Henning, Karl Heinz Missing: * Slawomir Jaranowski * Tamás Cservanák Also please CC post on private pmc list. Kind regards Karl Heinz +2nb: Delany PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release to the board report. Thanks T - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 4.0.0-alpha-7
Hi, I've tested several projects with it and also in relationship with Maven 3.9.X.. The same as in Maven 3.9.3 .. plugins used which have issues like the maven-site-plugin (3.12.1) and being reported via `-Dmaven.plugin.validation=VERBOSE` (in Maven 3.9.3) will not produce even a hint in Maven 4.0.0-alpha-7 without the supplemental parameter "-Dmaven.plugin.validation=VERBOSE" My opinion is to report such plugins in Maven 4 always to make sure people and more important plugin maintainers/author becoming aware of possible issues...or maybe reporting it already in 3.9.3 as well as in Maven 4.X Furthermore related to https://issues.apache.org/jira/browse/MNG-7228 rechecked and confirming that it now works. https://issues.apache.org/jira/browse/MNG-7604 * We have now surefire/failsafe 3.X versions related to pom.* interpolations. We might think about failing the build if finding such things * MNG-5600 Dependency management import should support exclusions. From my point of view this means we have to change the model version because that can technically being read by Maven 3.X but it simply will not work at all. * MNG-7805 This means we introduce NS but Maven 3.X can not read it anymore. That requires modelVersion change to fail Maven 3.X very early (Also XSD has to be changed for tools/IDE's etc.) I don't know how Maven 3.X behaves in cases of NS in the XML * Also found that the hint at the beginning of Maven 4 build: "Unable to find the root directory. Create a .mvn directory in the root directory or add the root="true" attribute on the root project's model to identify it." If I add that attribute to the ` I'm starting a new vote to release this new alpha. 67 issues solved: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353052 Staging repository: https://repository.apache.org/content/repositories/maven-1970 Dev dist directory: https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-7/ Source release checksums: apache-maven-4.0.0-alpha-6-src.zip sha512: bc822a381f84b156f2d5c2b59502db44ef3e8689f534913820dc0c68014e02dc75639c1990df4203d7923318d2b1668b050f452556c15eb638271e1ae3688e87 apache-maven-4.0.0-alpha-6-src.tar.gz sha512: c7e9d13df74797163e816536e76f14c25496cdc8f13faa990bf14ce5a5669ec09cdc44dd4da866dd72d68ba9e2d8d6bdcce57110e21ecbeb8d15c50cad64430b Binary release checksums: apache-maven-4.0.0-alpha-6-bin.zip sha512: ec47b84cbf5dd85a8081d218bf105d4664e298d906c28f11192bf563f30087a4d898f872fc73230391579f8aa84e70bddb0ae2eabc42b53a2c574d5793ceb1a2 apache-maven-4.0.0-alpha-6-bin.tar.gz sha512: 9959e537712167094a7909006168404c16b0788862311ef65840f5b8d3afc519e63262b064db7361bc6ef77940bed14ead5e0a59d135bcdeea83be4d9893 Staged site: https://maven.apache.org/ref/4-LATEST/ Draft for release notes: https://github.com/apache/maven-site/pull/432 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72h [ ] +1 [ ] +0 [ ] -1 Mit freundlichem Gruß Karl Heinz Marbaise -- SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 Inhaber Dipl.Ing.(FH) Karl Heinz Marbaise USt.IdNr: DE191347579 Hauptstrasse 177 52146 Würselen https://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.9.3
Hi,
difference between Maven 3.9.2, getting the following output: (mvn clean
verify):
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.397 s
[INFO] Finished at: 2023-06-25T11:48:38+02:00
[INFO]
[WARNING]
[WARNING] Plugin validation issues were detected in 2 plugin(s)
[WARNING]
[WARNING] * org.jacoco:jacoco-maven-plugin:0.8.10
[WARNING] * org.apache.maven.plugins:maven-site-plugin:3.12.1
[WARNING]
[WARNING] For more or less details, use 'maven.plugin.validation'
property with one of the values (case insensitive): [BRIEF, DEFAULT,
VERBOSE]
[WARNING]
This is a good conclusion at the end of the build.
Now using Maven 3.9.3:
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 2.321 s
[INFO] Finished at: 2023-06-25T11:49:01+02:00
[INFO]
Not even the smallest hint.
If I change the calling for Maven 3.9.3: (mvn clean verify
-Dmaven.plugin.validation=VERBOSE):
[INFO]
[INFO] --- jacoco:0.8.10:report (default) @ jdk21 ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[WARNING]
[WARNING] Plugin [INTERNAL, EXTERNAL] validation issues were detected in
following plugin(s)
[WARNING]
[WARNING] * org.apache.maven.plugins:maven-site-plugin:3.12.1
[WARNING] Declared at location(s):
[WARNING]* com.soebes.smpp:smpp:6.0.3
(/Users/khm/.m2/repository/com/soebes/smpp/smpp/6.0.3/smpp-6.0.3.pom) @
line 580
[WARNING] Plugin EXTERNAL issue(s):
[WARNING]* Plugin depends on the deprecated Maven 2.x compatibility
layer, which will be not supported in Maven 4.x
[WARNING] Mojo EXTERNAL issue(s):
[WARNING]* Mojo site:attach-descriptor
(org.apache.maven.plugins.site.descriptor.SiteDescriptorAttachMojo)
[WARNING] - Parameter 'localRepository' uses deprecated parameter
expression '${localRepository}': ArtifactRepository type is deprecated
and its use in Mojos should be avoided.
[WARNING]
[WARNING]
[WARNING] Fix reported issues by adjusting plugin configuration or by
upgrading above listed plugins. If no upgrade available, please notify
plugin maintainers about reported issues.
[WARNING] For more or less details, use 'maven.plugin.validation'
property with one of the values (case insensitive): [NONE, INLINE,
SUMMARY, BRIEF, VERBOSE]
[WARNING]
The interesting part here is that the jacoco-maven-plugin is NOT
reported at all for Maven 3.9.3.
Does that mean the jacoco-maven-plugin is ok or not? Or was the
reporting in Maven 3.9.2 wrong?
From my point of view the difference in behaviour is confusing...
+1 from me
Kind regards
Karl Heinz Marbaise
On 23.06.23 15:33, Tamás Cservenák wrote:
Howdy,
We solved 22 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353255
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-1968/
Dev dist directory:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.3/
Source release checksums:
apache-maven-3.9.3-src.zip sha512:
a56a9e47e70ba8e3e83ff627b76a712c7b5bda59245d23bcbc541b2358b859f699d4916b7e715c45a5c336676b8b2ab0ab472dffc045ae4db635b21f7ddcc0c2
apache-maven-3.9.3-src.tar.gz sha512:
5511b20c36fd09a8ba7260bfa78d29bb683a04828c56e93d176768eb61cb07ab91f29db745460ce9784c84561f359497158f4c800142716d3e590ac2c333e8fb
Binary release checksums:
apache-maven-3.9.3-bin.zip sha512:
fba80f4bb0429052d558959b1bfbc99984f8cb8ff59a53baae0a0874b71a2601e2805c5e557b7b59d81716a0b4b35d1b2eeccb566c40b23cc575331a4984ef6c
apache-maven-3.9.3-bin.tar.gz sha512:
400fc5b6d000c158d5ee7937543faa06b6bda8408caa2444a9c947c21472fde0f0b64ac452b8cec8855d528c0335522ed5b6c8f77085811c7e29e1bedbb5daa2
Staged site:
https://maven.apache.org/ref/3-LATEST/
Draft for release notes:
https://github.com/apache/maven-site/pull/424
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] Release Maven WAR Plugin version 3.4.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 11.06.23 22:14, Michael Osipov wrote: Hi, we solved 17 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12350597 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MWAR/issues Staging repo: https://repository.apache.org/content/repositories/maven-1955/ https://repository.apache.org/content/repositories/maven-1955/org/apache/maven/plugins/maven-war-plugin/3.4.0/maven-war-plugin-3.4.0-source-release.zip Source release checksum(s): maven-war-plugin-3.4.0-source-release.zip sha512: ef7b2621697024570522a778318106f1e5ca18bf6944cb9e43e693e8c37312af272036f517d03b3555622f9bad695217ececa078affda6442d76063b5153f998 Staging site: https://maven.apache.org/plugins-archives/maven-war-plugin-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 Mit freundlichem Gruß Karl Heinz Marbaise -- SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 Inhaber Dipl.Ing.(FH) Karl Heinz Marbaise USt.IdNr: DE191347579 Hauptstrasse 177 52146 Würselen https://www.soebes.de - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
Hi to all, The most recent version of Tomcat 11.0.0-M7 has lifted it's JDK minimum to JDK21 !!! https://tomcat.apache.org/tomcat-11.0-doc/changelog.html#Tomcat_11.0.0-M7_(markt) Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE} Maven Build Cache Extension 1.0.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 06.06.23 13:51, Olivier Lamy wrote: Hi, I'd like to release Maven Build Cache Extension 1.0.1 We fixed 13 issues https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352469=Text=12324820=Create Staging repo: https://repository.apache.org/content/repositories/maven-1953/ source zip: https://repository.apache.org/content/repositories/maven-1953/org/apache/maven/extensions/maven-build-cache-extension/1.0.1/maven-build-cache-extension-1.0.1-source-release.zip stages site: https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/ Vote open 72h +1 0 -1 cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
Hi, On 03.06.23 11:46, Hervé Boutemy wrote: +1 I really don't what benefit we get from going to Java 17 which was already part of the email: > Based on the argument we don't need features of JDK17+ I see a number > of things which could make our handling/maintenance easier for example > using sealed classes to prevent exposing internal things to public which > could be used etc. also some other small features (`var` for example; > Text-Blocks in Tests etc) or using records in some situation (really immutability).. > > Kind regards Karl Heinz Marbaise I perfectly see the impact we'll have on our users: for what benefit? notice that this will also impact all plugins: and given the few work done on plugins to clearly show what plugin version remains compatible with a JDK release, I feel we're not taking the topic the right way Le vendredi 2 juin 2023, 01:50:53 CEST Hunter C Payne a écrit : I'm not sure I would worry too much about that David. I think most devs who want better syntax moved from Java sometime ago. They might still be on the JVM just not writing Java. Also, Maven is a mature project. I don't think devs considering contributing to it are thinking about using the latest and greatest version of Java. Compatibility is probably a bigger concern for the user base. Just my opinion. Hunter On Thursday, June 1, 2023 at 04:17:26 PM PDT, David Jencks wrote: I wonder if having maven require java 8 syntax discourages any potential contributors who are used to coding using more recent developments. I have no idea how to tell, but maybe someone else does. David Jencks On Jun 1, 2023, at 3:02 PM, Karl Heinz Marbaise wrote: Hi, my clear opinion is to go with most recent JDK LTS version for the release point of Maven 4.0.0 which I assume will be JDK 21... That means clear the build time requirement which is completely different from runtime of an application. Older JDK's are supported by some vendors by having particular special support which most of the time requires special contracts (means also paying money for it)..some of them offering builds without paying money yes.. Older runtime target are supported with different approaches like Toolchain or via `--release XX` which exists since JDK9+. Furthermore if someone is not capable of upgrading the build environment to JDK9+ they can continue to use Maven 3.8.X or Maven 3.9.X... If it would be requirement to port things back to 3.8.X or 3.9.X it could be handled by someone who has the time etc. to do that ... if not, those people might think of paying someone to do that work... The given argument about JPMS for migration causes issues is from my point of view false-positive because migration to newer JDK versions does not require JPMS usage... Even platforms like AWS support JDK17 in the meantime which is the runtime... Based on the maintenance part it would mean in consequence to downgrade to even JDK7... (or even lower) because you can get support for older JDK version in some ways... (JDK7 from azul for example) Kind regards Karl Heinz Marbaise [1] https://www.oracle.com/java/technologies/java-se-support-roadmap.html - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
On 05.06.23 13:55, Romain Manni-Bucau wrote: Hi Le lun. 5 juin 2023 à 13:22, Elliotte Rusty Harold a écrit : On Sun, Jun 4, 2023 at 10:59 AM Delany wrote: I think the point I'm making is no-one wants to write in an older version of the language they started writing in. Its tedious. Anyone who started writing java11 code is going to have a hard time accepting they need to write in java8, just as a java8 will bulk at writing in java5. Of course for the oldies it just feels nostalgic. Strongly disagree. I personally would strongly prefer to stick to Java *7*, although these days I use mostly 8 and 11. IMHO Java 8 and Java 11 were significant downgrades for clarity of code and ease of use. While there were some nice improvements in libraries and VM in those versions, they are completely swamped by the truly awful lambda syntax and the useless pain of the Java Platform Module System. This is a very interesting feedback cause we had the exact same on some other ASF feedback in early lambdas days and today it is completely gone so I guess it is just a habit thing. So the point is either: do you fight against the scale of time or not and if so is it ok for an asf project to reject potential contributors (because it is what it means in practise, in particular when java 7 becomes hard to get). I second that... even today... Note: I fully agree JPMS is useless but I also fully agree we don't need to embrace it, it will not even be enabled until plexus-container does support it, but it does not hurt, rest is more than fine and the new GC helps in a software like maven. Nor is it like we've finished the work of migrating onto Java 8. Just this past week I replaced some code that hasn't been needed since Java *1.4*. This is a good point, my personal view on that is we had way too much abstraction for the actual codepath we use so I would be +1 to drop most of the deps we rely on to include a core and limited set in maven project, this will help upgrades instead of having to rely on 50+ projects - indeed just my 2cts. Migrating to still newer Java versions is a distraction from far more important work. We haven't even moved all the plugins off Java 7 yet. The burden of proof is on people who want to migrate to Java 17 to show how that will improve the project. That burden has not been met. Nobody requested to migrate the code base, IMHO the points were mainly: 1. enable to use a "not too old" base version to keep it easy to contribute and leverage interesting new features (note: not always API) 2. use an up to date and evolutive version (java 8 doesnt get all backports these days, even in maintained distro so you can end up accessing a http maven repo which is not supported depending the JVM you use) Yep.. 3. reduce the compatibility matrix right now since part of it is no more useful for projects which will embrace mvn 4 Just build on most recent version of available JDK... and generate for the target platform for example 11 (via --release).. 4. ensure you can upgrade dependencies and do no have to stick to deprecated versions (libs started to drop java 8 support already) That's another good point.. So yes Java 17 will not solve most of our issues but Java 8-21 support we need to have already creates some in terms of validations, PR feedback, and community message IMHO. Since java 8 is covered by 3.9 I don't see why we would not take the opportunity to move forward, syntax and details like that are a great opportunity to learn for everybody more than a drawback from my past experience and being able to use a reliable - cause we know it is supported in the min version we use - http11 client with a better protocol support is also important even if API didn't change much. Yes Maven 3.9 or maybe 3.8.X will support JDK8... so no problem. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Question - JDK Minimum of future Apache Maven 4.0.0
Hi, On 05.06.23 13:21, Elliotte Rusty Harold wrote: On Sun, Jun 4, 2023 at 10:59 AM Delany wrote: I think the point I'm making is no-one wants to write in an older version of the language they started writing in. Its tedious. Anyone who started writing java11 code is going to have a hard time accepting they need to write in java8, just as a java8 will bulk at writing in java5. Of course for the oldies it just feels nostalgic. Strongly disagree. I personally would strongly prefer to stick to Java *7*, > although these days I use mostly 8 and 11. IMHO Java 8 and Java 11 were significant downgrades for clarity of code and ease of use. Ok... my experience is completely different... working from the beginning on JDK8 after first GA of JDK11 on JDK 11 and now on JDK17 ... also JDK 18...20 etc. At the moment experimenting with JDK21... While there were some nice improvements in libraries and VM in those versions, they are completely swamped by the truly awful lambda syntax and the useless pain of the Java Platform Module System. The JPMS is opt-in NOT opt-out.. and useless depends on the point of view... Lambda syntax etc. is a thing you should get used to... if not it's fine don't use it... Nor is it like we've finished the work of migrating onto Java 8. Have we really decided to "migrate" to Java 8? We are changing code when someone is working on it and willing to do that ... if not it's fine too... It takes time to migrate that size of code base which is fine to do that step by step and not as a big-bang part... because at that time can be decided to use newer language features (if they make sense).. > Just this past week I replaced some code that hasn't been needed since Java *1.4*. That's very good... Migrating to still newer Java versions is a distraction from far more important work. We are an open source project and anyone can work on anything a person would like to work on... And what is the important work ? > We haven't even moved all the plugins off Java 7 yet. The burden of proof is on people who want to migrate to Java 17 to show how that will improve the project. That burden has not been met. So there is a need to prove that JDK17 is better for the project than getting further and further behind... From my point of view JDK11+ already proven that in itself... because we gain performance (CDS or something like CraC etc), less memory.. which can improved by using JDK11+ language features etc. also making things visible which only need to (JDK17: sealed classes without the hard jump to the JPMS)... BTW: Other projects already moved that path ... for example Maven Tycho Project starting with 3.0.0 requires JDK17 as minimum Also mentioning (several times) Spring Boot 3.0+ etc. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Project Info Reports Plugin version 3.4.5
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 03.06.23 15:10, Michael Osipov wrote: Hi, we solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12353297 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPIR/issues Staging repo: https://repository.apache.org/content/repositories/maven-1951/ https://repository.apache.org/content/repositories/maven-1951/org/apache/maven/plugins/maven-project-info-reports-plugin/3.4.5/maven-project-info-reports-plugin-3.4.5-source-release.zip Source release checksum(s): maven-project-info-reports-plugin-3.4.5-source-release.zip sha512: 75631dc43b83190bceab61f7311d620824bf1d8c8efd406014c287021fa4aeedb6fc40fd111f8ecc7c742bc1ae55ba039fec65bb3bba3cf6a8f514cb9bbc44e6 Staging site: https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-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 Surefire version 3.1.2
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 03.06.23 21:32, Michael Osipov wrote: Hi, we solved 15 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12353294 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-1952/ https://repository.apache.org/content/repositories/maven-1952/org/apache/maven/surefire/surefire/3.1.2/surefire-3.1.2-source-release.zip Source release checksum(s): surefire-3.1.2-source-release.zip sha512: 18be516e0d43673fa9c6754f34a90138d9fac58b81267b81cf9ce0401389c63570dec5b4eea350c939ea9ed599ccc14a7be60fd7517b897ce983c2ac3ca6207d Staging site: https://maven.apache.org/surefire-archives/surefire-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 Apache Maven Release Plugin version 3.0.1
Hi, +1 from me, Kind regards Karl Heinz Marbaisew On 30.05.23 23:34, Slawomir Jaranowski wrote: Hi, We solved 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-1950/ https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip Source release checksum(s): maven-release-3.0.1-source-release.zip - SHA-512: e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69 Staging site: https://maven.apache.org/components/maven-release-archives/maven-release-LATEST Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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: Question - JDK Minimum of future Apache Maven 4.0.0
Hi, my clear opinion is to go with most recent JDK LTS version for the release point of Maven 4.0.0 which I assume will be JDK 21... That means clear the build time requirement which is completely different from runtime of an application. Older JDK's are supported by some vendors by having particular special support which most of the time requires special contracts (means also paying money for it)..some of them offering builds without paying money yes.. Older runtime target are supported with different approaches like Toolchain or via `--release XX` which exists since JDK9+. Furthermore if someone is not capable of upgrading the build environment to JDK9+ they can continue to use Maven 3.8.X or Maven 3.9.X... If it would be requirement to port things back to 3.8.X or 3.9.X it could be handled by someone who has the time etc. to do that ... if not, those people might think of paying someone to do that work... The given argument about JPMS for migration causes issues is from my point of view false-positive because migration to newer JDK versions does not require JPMS usage... Even platforms like AWS support JDK17 in the meantime which is the runtime... Based on the argument we don't need features of JDK17+ I see a number of things which could make our handling/maintenance easier for example using sealed classes to prevent exposing internal things to public which could be used etc. also some other small features (`var` for example; Text-Blocks in Tests etc) or using records in some situation... Based on the maintenance part it would mean in consequence to downgrade to even JDK7... (or even lower) because you can get support for older JDK version in some ways... (JDK7 from azul for example) Kind regards Karl Heinz Marbaise [1] https://www.oracle.com/java/technologies/java-se-support-roadmap.html - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: GH issues and GH discussions
Hi, On 29.05.23 15:50, Christoph Läubrich wrote: I must confess "another central project" do not feels right: 1) there already is a "central" one everyone can easily find if searching for "maven github": https://github.com/apache/maven/ That does not help here because that project is Maven itself (maven core)... which will produce much more confusion from my POV. 2) for "subprojects" its usually better to discuss things close where the code is In general yes ... but unfortunately many people do not see the need focus for that...(https://maven.apache.org/plugins/) shows every project with link to appropriate GH projects etc... Please note that some feature in GH do not work well across repositories (e.g. embedding code snippets in issues), also I don't see any advantage in scattering things around. Yes that is a real problem with GH issues etc. Having a "central place "where contributors need to watch out and move things around or need to find out what the topic is about will make things more confusing, usually users are quite familiar with finding the right place. I have different experiences... If one wants to group things more, it would be better to have an apache-maven organization on gihub and move all maven related there (the one can also have organization readme, pinned repositories and so on), this works quite well (e.g. Eclipse Foundation uses that approach). Yes that might be a better solution going via a Apache Maven Project Organisation ... +1 for that... But in the end it will not solve the problem to redirect the people to the "correct" project Kind regards Karl Heinz Marbase Am 29.05.23 um 13:50 schrieb Karl Heinz Marbaise: Hi, I would suggest to create an umbrella project like: apache-maven-project on github and make it the central starting point for users... to ask question (discussions) and optionally reroute them to the appropriate github repos... In general I agree to the tendency to use GH issues etc. instead of JIRA based on the hurdles which exists (for a lot of reasons)... I second Hervé's suggestion to write down the needed/practical steps ... and start going...what about things currently in JIRA and needed to be migrated moved etc. ..We have a large history in JIRA... To fulfill the formalism (also have documented the decision here on the ML) we should start simply a VOTE to get an in general decision about moving to GH-issues to leave JIRA behind... (not about the details) that can be done later on...(for example using GH discussions etc.) afterwards we can decide with which project we would like to start and fiddle the details. Kind regards Karl Heinz Marbaise On 27.05.23 09:22, Hervé Boutemy wrote: on testing GH issues migration from Jira: yes cache-extension [1] looks like an interesting example, given it has a small history with its Jira content we also have mvnd which uses GH issues from the start: testing and making clear practices on release and release notes could also be worked there [2] we'll need to write down what practical steps such a migration requires => probably a good fit for our Wiki, where we already organized equivalent updates in the past [3] on using GH discussions, I suppose this should be an independent next discussion [1] https://github.com/apache/maven-build-cache-extension [2] https://github.com/apache/maven-mvnd [3] https://cwiki.apache.org/confluence/display/MAVEN/Maven+Infrastructure Le vendredi 26 mai 2023, 09:44:00 CEST Olivier Lamy a écrit : Hi, This has been already discussed in the past. But due to recent changes in ASF Jira infrastructure (limitation of Jira users, validation of account creation). Maybe we could reconsider moving from Jira to GH issues and why not simplify the workflow as well. I imagine not having to create an issue if a PR exists first (sounds like duplicate work). By the way, release notes will be automatically created from PRs. (could be manually modified if a change doesn't have a PR). Regarding migration, we can start project by project. Few options: - extreme simplicity, do not migrate any data (just mark the Jira project as read only with a banner/link to corresponding gh issues). If someone really needs an issue to get fixed he will clone it to GH - middle complexity, migrate only open issues (components moved as a label) - extreme complexity, migrate all issues of a project (components moved as a label and version created) We can start by small projects such as cache-extension and one plugin (compiler?) Regarding GH discussions, maybe we can open discussions for https://github.com/apache/maven which sounds like a natural place for users to go. (discussions could be mirrored to a ML) I do not have a strong opinion here, but I feel like opening discussions for every single repo will be complicated to follow up. WDYT? cheers Olivier ---
Re: GH issues and GH discussions
Hi, On 29.05.23 14:07, Michael Osipov wrote: Am 2023-05-29 um 13:50 schrieb Karl Heinz Marbaise: Hi, I would suggest to create an umbrella project like: apache-maven-project on github and make it the central starting point for users... to ask question (discussions) and optionally reroute them to the appropriate github repos... In general I agree to the tendency to use GH issues etc. instead of JIRA based on the hurdles which exists (for a lot of reasons)... I second Hervé's suggestion to write down the needed/practical steps ... and start going...what about things currently in JIRA and needed to be migrated moved etc. ..We have a large history in JIRA... To fulfill the formalism (also have documented the decision here on the ML) we should start simply a VOTE to get an in general decision about moving to GH-issues to leave JIRA behind... (not about the details) that can be done later on...(for example using GH discussions etc.) afterwards we can decide with which project we would like to start and fiddle the details. Before we do that, we need to aggressively go through all tickets and closes issues which we will never address or are invalid by now. M Yep good idea +1 for that. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire version 3.1.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 28.05.23 23:24, Michael Osipov wrote: Hi, we solved 9 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12353266 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-1949/ https://repository.apache.org/content/repositories/maven-1949/org/apache/maven/surefire/surefire/3.1.1/surefire-3.1.1-source-release.zip Source release checksum(s): surefire-3.1.1-source-release.zip sha512: deb15c554f2c86814cc834de016e9c4559ab33233ed02fd1291bf5119e23bfd27b862f6876b6e0914f950f92e1893f62a41027a802d4df11cc30d146a91060d0 Staging site: https://maven.apache.org/surefire-archives/surefire-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: GH issues and GH discussions
Hi, I would suggest to create an umbrella project like: apache-maven-project on github and make it the central starting point for users... to ask question (discussions) and optionally reroute them to the appropriate github repos... In general I agree to the tendency to use GH issues etc. instead of JIRA based on the hurdles which exists (for a lot of reasons)... I second Hervé's suggestion to write down the needed/practical steps ... and start going...what about things currently in JIRA and needed to be migrated moved etc. ..We have a large history in JIRA... To fulfill the formalism (also have documented the decision here on the ML) we should start simply a VOTE to get an in general decision about moving to GH-issues to leave JIRA behind... (not about the details) that can be done later on...(for example using GH discussions etc.) afterwards we can decide with which project we would like to start and fiddle the details. Kind regards Karl Heinz Marbaise On 27.05.23 09:22, Hervé Boutemy wrote: on testing GH issues migration from Jira: yes cache-extension [1] looks like an interesting example, given it has a small history with its Jira content we also have mvnd which uses GH issues from the start: testing and making clear practices on release and release notes could also be worked there [2] we'll need to write down what practical steps such a migration requires => probably a good fit for our Wiki, where we already organized equivalent updates in the past [3] on using GH discussions, I suppose this should be an independent next discussion [1] https://github.com/apache/maven-build-cache-extension [2] https://github.com/apache/maven-mvnd [3] https://cwiki.apache.org/confluence/display/MAVEN/Maven+Infrastructure Le vendredi 26 mai 2023, 09:44:00 CEST Olivier Lamy a écrit : Hi, This has been already discussed in the past. But due to recent changes in ASF Jira infrastructure (limitation of Jira users, validation of account creation). Maybe we could reconsider moving from Jira to GH issues and why not simplify the workflow as well. I imagine not having to create an issue if a PR exists first (sounds like duplicate work). By the way, release notes will be automatically created from PRs. (could be manually modified if a change doesn't have a PR). Regarding migration, we can start project by project. Few options: - extreme simplicity, do not migrate any data (just mark the Jira project as read only with a banner/link to corresponding gh issues). If someone really needs an issue to get fixed he will clone it to GH - middle complexity, migrate only open issues (components moved as a label) - extreme complexity, migrate all issues of a project (components moved as a label and version created) We can start by small projects such as cache-extension and one plugin (compiler?) Regarding GH discussions, maybe we can open discussions for https://github.com/apache/maven which sounds like a natural place for users to go. (discussions could be mirrored to a ML) I do not have a strong opinion here, but I feel like opening discussions for every single repo will be complicated to follow up. WDYT? cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M7
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.04.23 14:04, Michael Osipov wrote: Hi, IMPORTANT: Requires Doxia Sitetools 2.0.0-M8 and Maven Reporting Impl 4.0.0-M7 vote/staging repo! we solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353122 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-exec Staging repo: https://repository.apache.org/content/repositories/maven-1917/ https://repository.apache.org/content/repositories/maven-1917/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M7/maven-reporting-exec-2.0.0-M7-source-release.zip Source release checksum(s): maven-reporting-exec-2.0.0-M7-source-release.zip sha512: 45c09d787eaba789108fd2ae653ffd10d1b793b1924a21172a11c45d9c006b0e4517efdf7ba94b2bad74cc50f14ee49db9223e1b6c3bf1b8f92a14b2aff7 Staging site: https://maven.apache.org/shared-archives/maven-reporting-exec-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M8
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.04.23 13:26, Michael Osipov wrote: Hi, we solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12353110 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open Staging repo: https://repository.apache.org/content/repositories/maven-1915 https://repository.apache.org/content/repositories/maven-1915/org/apache/maven/doxia/doxia-sitetools/2.0.0-M8/doxia-sitetools-2.0.0-M8-source-release.zip Source release checksum(s): doxia-sitetools-2.0.0-M8-source-release.zip sha512: 3e81ea13d4acfebdbbfd04f9a0f1ba0d119f6c5c9e152b1838c858339889205e92acc1f42a254223f0c195a6fce802edcc5753e16623875b4284e9142c17116c Staging site: https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Project Info Reports Plugin version 3.4.3
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.04.23 16:45, Michael Osipov wrote: Hi, we solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12352922 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MPIR/issues Staging repo: https://repository.apache.org/content/repositories/maven-1918/ https://repository.apache.org/content/repositories/maven-1918/org/apache/maven/plugins/maven-project-info-reports-plugin/3.4.3/maven-project-info-reports-plugin-3.4.3-source-release.zip Source release checksum(s): maven-project-info-reports-plugin-3.4.3-source-release.zip sha512: c2472a858995778c80a21a7b15c0353f571a268506c9b514737785287129b9d101cd78a8b5447badf774df9e6fe8a7501f492abbf9c815cf8c6e374bd0be709a Staging site: https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M7
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.04.23 13:41, Michael Osipov wrote: Hi, IMPORTANT: Requires Doxia Sitetools 2.0.0-M8 vote/staging repo! we solved 3 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353116 There are a few issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl Staging repo: https://repository.apache.org/content/repositories/maven-1916/ https://repository.apache.org/content/repositories/maven-1916/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M7/maven-reporting-impl-4.0.0-M7-source-release.zip Source release checksum(s): maven-reporting-impl-4.0.0-M7-source-release.zip sha512: 9f0251cd1e04fd164402a7bcb4c1d21b28585b5abdfeb9f5b3b66825ef927f322e2eb85a1ddcaf5040c6afc5d08e98f4318b889f4701aef639d8d95fb8fd7808 Staging site: https://maven.apache.org/shared-archives/maven-reporting-impl-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Shared JAR version 3.0.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.04.23 18:02, Slawomir Jaranowski wrote: Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12335470 There are no issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-shared-jar Staging repo: https://repository.apache.org/content/repositories/maven-1919/ https://repository.apache.org/content/repositories/maven-1919/org/apache/maven/shared/maven-shared-jar/3.0.0/maven-shared-jar-3.0.0-source-release.zip Source release checksum(s): maven-shared-jar-3.0.0-source-release.zip - SHA-512 : f290c743eb8675c6052709d431f8ba59de6c2e06749e9617386ea5ce7a505e822157ade7ce9459996ae6f71bb7a83689cd884358704207e27c154da7c5bf1602 Staging site: https://maven.apache.org/shared-archives/maven-shared-jar-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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: [HEADS UP] ASF/Maven parent poms
On 13.04.23 21:35, Slawomir Jaranowski wrote: Hi. I would like to release the next version of parent poms. ASF - https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20fixVersion%20%3D%20ASF-30 Maven - https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20fixVersion%20%3D%20MAVEN-40 With already merged changes we can start using JDK 20 for builds. Great... Issues to discus: ASF: MPOM-398 - Bump maven-help-plugin from 3.3.0 to 3.4.0 - 3.4.0 requires Maven 3.6.3, but whole build requires 3.2.5 it is some of inconsistency for me MPOM-289 - Use properties to define the versions of plugins - I hope it can be useful MPOM-344 - we need a new release of maven-remote-resources-plugin MPOM-394 - we need a new release of Maven Project Info Reports Plugin to 3.4.3 Maven: MPOM-414 - newer version of spotless require JDK 11+ We could build with JDK11 or even JDK17 and use "--release" to produce JDK8 compatible code... ? Kind regards Karl Heinz Marbaise Please comment / discuss in jira because we many case and on ML we can introduce a mess - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Invoker Plugin version 3.5.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 27.03.23 22:29, Slawomir Jaranowski wrote: Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12352974 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1905/ https://repository.apache.org/content/repositories/maven-1905/org/apache/maven/plugins/maven-invoker-plugin/3.5.1/maven-invoker-plugin-3.5.1-source-release.zip Source release checksum(s): maven-invoker-plugin-3.5.1-source-release.zip - SHA-512 : b0d1972546bdc94f100e18ea4ec502c747559f3ea2de779e29e164cc2d3a4f444c0277dd2143a0b21e81efb8e948f87d06d8617f278840a58aacdccd6ee4482f Staging site: https://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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: [HEADS UP] Maven Release 3.0.0
Hi, go for it... +1 Kind regards Karl Heinz Marbaise On 15.03.23 13:52, Michael Osipov wrote: Folks, Maven Release 3.0.0 is almost complete, Maven SCM 2.0.0 will be the last ticket from my PoV. I'll leave people a couple of days to discuss open issue, if necessary. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.9.1
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.03.23 11:14, Tamás Cservenák wrote: Howdy, We solved 29 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352872 There are still 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-1888/ Dev dist directory: https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.1/ Source release checksums: apache-maven-3.9.1-src.zip sha512: 2b1f14d4d5fd4a9759ac2519dd8eb4fbfdec199a9fdc66b7995b606bb5548c4f10f431d02e725f10af4d89d55d575e6d8bc7c2e006bbfbbaa0f6349cfd699f9b apache-maven-3.9.1-src.tar.gz sha512: 726679381d4660150f88a727e16005cecd0fee6c03748ae8db889cfe88a2da7ac378f0d221bf237953bba3c49542d2bd7233888eb549cf7c10dd4e2deb2a3828 Binary release checksums: apache-maven-3.9.1-bin.zip sha512: 4ae5a0d17f9e6cbe57640c481f426a9184dfb451c2bb7cc7db324da095f616a14e7c482a79240e5286e241d8cd2805ea1cd9c95e38954101c2fa4088baad9a1a apache-maven-3.9.1-bin.tar.gz sha512: d3be5956712d1c2cf7a6e4c3a2db1841aa971c6097c7a67f59493a5873ccf8c8b889cf988e4e9801390a2b1ae5a0669de07673acb090a083232dbd3faf82f3e3 Staged site: https://maven.apache.org/ref/3-LATEST/ Draft for release notes: https://github.com/apache/maven-site/pull/400 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] Release Apache Maven 4.0.0-alpha-5
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.03.23 18:14, Guillaume Nodet wrote: Hey We solved 26 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352862=12316922 Staging repository: https://repository.apache.org/content/repositories/maven-1890 Dev dist directory: https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-5/ Staged site: https://maven.apache.org/ref/4-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Please review and vote ! Cheers, Guillaume Nodet - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Help Plugin version 3.4.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 14.03.23 22:39, Slawomir Jaranowski wrote: Hi, We solved 11 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522=12352206 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPH%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1887/ https://repository.apache.org/content/repositories/maven-1887/org/apache/maven/plugins/maven-help-plugin/3.4.0/maven-help-plugin-3.4.0-source-release.zip Source release checksum(s): maven-help-plugin-3.4.0-source-release.zip - SHA-512 : eba7abf7b99f81f592c48a03b5d6008ef556500e21fbc86fc01b750112c6a459729c6743ac1daeb80d941378f9207ec23095bd2477387578369c4d29d8053271 Staging site: https://maven.apache.org/plugins-archives/maven-help-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 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 SCM version 2.0.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 15.03.23 13:29, Michael Osipov wrote: Hi, We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828=12353002 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/SCM/issues Staging repo: https://repository.apache.org/content/repositories/maven-1889/ https://repository.apache.org/content/repositories/maven-1889/org/apache/maven/scm/maven-scm/2.0.0/maven-scm-2.0.0-source-release.zip Source release checksum(s): maven-scm-2.0.0-source-release.zip sha512: 508ad802e8570014c473abc28b2e36df004ead19ed4325f81db98709daa6577311b94cf10bf6b8e6d4c5a947dd06357564a47491707bcc3d5d57ae506eb238d1 Staging site: https://maven.apache.org/scm-archives/scm-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 Apache Maven Surefire/Failsafe Plugin version 3.0.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 11.03.23 10:08, Slawomir Jaranowski wrote: Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12352998 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1886/ https://repository.apache.org/content/repositories/maven-1886/org/apache/maven/surefire/surefire/3.0.0/surefire-3.0.0-source-release.zip Source release checksum(s): surefire-3.0.0-source-release.zip - SHA-512 : 230fc6edc85d4c2f868c1044d545f07ec1435aed320959262c1fc855b5ef80dbd2f1f20dc6c6137664028d6049f950d75d10f8abe5f2f8f506c946459621c043 Staging site: https://maven.apache.org/surefire-archives/surefire-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Reverted a lot of commits on apache maven-site master
Hi, short question why are so many reverts done on the apache site master? from d7db85d3 (doc) added snippet types new f3f37282 Revert "(doc) added snippet types" new 763c0ed3 Revert "(doc) lint markdown files" new b0eb56dd Revert "[MNGSITE-509] Fix linking to anchors" new 55d05632 Revert "[MNGSITE-509] Fix linking in introduction-to-the-lifecycle.md" new 917e15fd Revert "Refresh - Guide to Developing Java Plugins" new 591a1fd2 Revert "many plugins released" new 7d348a3e Revert "reformt" new be357c6d Revert "fix JIRA link, reformt" new 7bafdd42 Revert "Maven Reporting Impl 4.0.0-M4 released" new 03e99ad1 Revert "use directory, not folder" new 9c5f1ff1 Revert "surefire 3.0.0-M9" new 10d6f9d9 Revert "[MNGSITE-507] [DOXIA-692] Improve conversion results - part2" new c61f169d Revert "[MNGSITE-507] [DOXIA-692] Improve conversion results" new 656d36f2 Revert "[MNGSITE-507] Converted .apt documents to Markdown" Can someone explain that... what is the reason for reverting so many commits on the site? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: CVEs in maven-compat via toolchains
Hi, On 14.02.23 11:22, Mark Derricutt wrote: Hey all, I was alerted the other day about a security issue with my clojure-maven-plugin apparently pulling in log4j 1.2, but using the dependency:tree plugin showed nothing. Seems this is due to dependencies being overridden by newer maven versions, anyway - I use toolchains in the plugin and have this dependency tree: ``` [INFO] +- org.apache.maven:maven-toolchain:jar:3.0-alpha-2:compile [INFO] | +- (org.apache.maven:maven-core:jar:3.0-alpha-2:compile - omitted for conflict with 3.9.0) [INFO] | \- org.apache.maven:maven-compat:jar:3.0-alpha-2:compile [INFO] | +- (org.apache.maven:maven-model:jar:3.0-alpha-2:compile - omitted for conflict with 3.9.0) [INFO] | +- (org.codehaus.plexus:plexus-container-default:jar:1.0-beta-3.0.5:compile - omitted for duplicate) [INFO] | +- (org.codehaus.plexus:plexus-component-annotations:jar:1.0-beta-3.0.5:compile - omitted for conflict with 1.5.5) ``` The version maven-toolchain 3.0-alpha-2 is of 2009 !!! https://search.maven.org/search?q=g:org.apache.maven%20a:maven-toolchain Also taken a look at: https://github.com/talios/clojure-maven-plugin/blob/develop/pom.xml which exactly shows this: org.apache.maven maven-toolchain 3.0-alpha-2 which I think is the culprit... The current version of toolchains-plugin: https://maven.apache.org/plugins/maven-toolchains-plugin/ The current ToolchainManager can be obtained from the maven-core (I would suggest to set minimum maven version to 3.2.5)...(Take a deeper look into maven-compiler-plugin)... Kind regards Karl Heinz Marbaise This trips up with: ``` [ERROR] org.apache.maven:maven-compat:jar:3.0-alpha-2:compile; https://ossindex.sonatype.org/component/pkg:maven/org.apache.maven/maven-compat@3.0-alpha-2?utm_source=ossindex-client_medium=integration_content=1.8.1 [ERROR] * [CVE-2021-26291] CWE-346: Origin Validation Error (9.1); https://ossindex.sonatype.org/vulnerability/CVE-2021-26291?component-type=maven=org.apache.maven%2Fmaven-compat_source=ossindex-client_medium=integration_content=1.8.1 ``` There doesn't appear to be a newer version of `maven-toolchain` at all - or is there and I'm just looking in the wrong place these days? Cheers, Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
