Building Maven Under JDK 24

Whilst Maven 4 is targeting Java 17, I see the build doesn’t seem to work under Java 24: [INFO] --- sisu:0.9.0.M3:main-index (index-project) @ maven-model-builder --- [INFO] [INFO] Reactor Summary for Apache Maven 4.0.0-rc-4-

Re: Building Maven Under JDK 24

Hi, did you try upgrading asm in plugin deps? Romain Manni-Bucau @rmannibucau | .NET Blog | Blog | Old Blog | Github | LinkedIn

Re: Building Maven Under JDK 24

On 20 Mar 2025 at 10:04:24 AM, Romain Manni-Bucau wrote: > did you try upgrading asm in plugin deps? > Nope - but a cursory glance shows asm 9.7.1 being used, which is the current version. -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree

Re: Building Maven Under JDK 24

On 20 Mar 2025 at 7:12:40 PM, Romain Manni-Bucau wrote: > Looks like the error says the opposite, did you check the plugin asm > version and not maven one? > > > Looks like the build is using 0.9.0.M3 of the issue-maven-plugin, which includes and embeded version of asm 9.6: https://github.com/e

Re: Building Maven Under JDK 24

Looks like the error says the opposite, did you check the plugin asm version and not maven one? Romain Manni-Bucau @rmannibucau | .NET Blog | Blog | Old Blog | Github <

Re: BOM / Imported BOM - Maven 4.0.0-rc3

Howdy, some tooling already exists: gav-dm-tree: https://gist.github.com/cstamas/7e3f8d444a74d9a2f4f7d7114af156bf gav-dm-list: https://gist.github.com/cstamas/419f4663744150b76f737cbd89fedf4f and the new "flatten bom" mojo. And my proposal is to "pre-digest" the BOM, not any BOM you consume, just

Re: BOM / Imported BOM - Maven 4.0.0-rc3

FTR Jira issues https://issues.apache.org/jira/browse/MNG-7906 https://issues.apache.org/jira/browse/MNG-7854 https://issues.apache.org/jira/browse/MPH-183 and all linked issues I don't know how this is relates with bom packaging in Maven 4 https://maven.apache.org/guides/introduction/introductio

Re: BOM / Imported BOM - Maven 4.0.0-rc3

Howdy, BOMs are "good things" when authored and used properly. Problem begins when BOMs authors start adding import statements to their authored BOMs. BOMs should be _flat_. Problem explained: * I as consumer "delegate" dep control to library I want to use, BUT * library BOM "delegate" dep contr

Re: BOM / Imported BOM - Maven 4.0.0-rc3

Le mer. 19 mars 2025 à 13:59, Tamás Cservenák a écrit : > Howdy, > > BOMs are "good things" when authored and used properly. > > Not really, it is if you have a single one but as soon as it needs 3rd party it is a mess even if well written or you need a bom for all project and flatten all your de

Re: BOM / Imported BOM - Maven 4.0.0-rc3

Can we step back a sec, what does bom bring that is not solved without? Dependency resolution is perfectly handled with type=pom (without scope=import), reusability with multiple scope is quite trivial with a property for the version and potentially the whole gav. At the end we can forbid (= stop s

Re: BOM / Imported BOM - Maven 4.0.0-rc3

If you need to digest a large 3rd party project you have to "know" all the internal versions of that project and/or its dependencies in some way. For example we import com.fasterxml.jackson:jackson-parent which fixes versions of about 60 artifacts. Of course we don't use all of those but if

Re: BOM / Imported BOM - Maven 4.0.0-rc3

Le mer. 19 mars 2025 à 14:21, Thomas Reinhardt a écrit : > > If you need to digest a large 3rd party project you have to "know" all > the internal versions of that project and/or its dependencies in some way. > Any reason to that? It was cleanly handled before bom without any issues. > > For e