cstamas commented on issue #11575: URL: https://github.com/apache/maven/issues/11575#issuecomment-3670034916
Given we play in two dimensions here (supported Java bytecode and supported Maven version), mixed with the fact that older Maven versions (due older Sisu with older ASM) would simply skip component bytecode that are not readable by it, component alone cannot do much about this "unsupported env error", if it is "more modern" (ie Java 17) and tried with older Maven (ie 3.6.3). Also, given build time requirement for Maveniverse projects are consistently 21 (ie latest LTS when it all started), and to make Java 21 to produce Java 8 output one uses `maven.compiler.release=8` as [explained here](https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-release.html), that same `8` was reused in this range as well, assuming is okay.... But seems now 😞 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
