You may be suffering from selection bias in your sample!
Here's an (old) StackOverflow post showing someone using enablePreview to
test out a new JDK12 feature (which answers the "use case") well.
https://stackoverflow.com/questions/52232681/compile-and-execute-a-jdk-preview-feature-with-maven
In
I just bumped the maven-compiler-plugin version on my project from 3.9.0 to
3.10.0 and it caused Windows-based builds to fail maven-bnd-plugin tests
for package-info files in the "wrong" directory. The symptom looks to be
associated with the windows file separator.
Sample failure looks like:
[INF
n.
>
> On Mon, Feb 14, 2022 at 10:56 AM Daniel B. Widdis
> wrote:
>
> > I just bumped the maven-compiler-plugin version on my project from 3.9.0
> to
> > 3.10.0 and it caused Windows-based builds to fail maven-bnd-plugin tests
> > for package-info files in the "
ing/speculation.
[1] - ClassVisitor (ASM 9.2) (ow2.io)
<https://asm.ow2.io/javadoc/org/objectweb/asm/ClassVisitor.html>
On Mon, Feb 14, 2022 at 1:40 PM Daniel B. Widdis wrote:
> I've confirmed this PR is the relevant problem as the symptoms can be
> s
quot;.java".length() )
I think I have enough info to file a Jira now.
[1] -
https://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html#jvms-4.2.1
On Mon, Feb 14, 2022 at 2:52 PM Daniel B. Widdis wrote:
> I believe I've traced the problem to the binary inside the generated
>
> My question is what is the correct/preferred/recommended way to do this?
Not combine shading and JPMS! :-)
But seriously. Have a look at Moditect. It has the capability of adding a
module-descriptor to a JAR after the fact, and may suit your needs. I
honestly can't think of any other sane wa
It's amusing when you come upon an error, google the error message, and
find an email thread you participated in and forgot about.
Resurrecting this thread from last July and hoping for some insight.
I last released my project using maven-release-plugin on July 20, 2022 with
no issues. My projec
Non-binding +1
On Wed, Apr 30, 2025 at 6:12 AM Matthias Bünger wrote:
> Hi everyone,
> over the last years we had several discussions about lifting the
> required Java version to run Maven from 8 to something higher. You can
> find them in the mail archive.
> In February 2024 we decided to lift
