Following "Maven Compiler Plugin 3.12.0 Released" [1] I'm trying it out
in a small project of mine [2]. After updating the
maven-compiler-plugin 3.11.0 -> 3.12.0 I've noticed the following error
occurring in my dirty(!) working copy:
> mvn -V package
Apache Maven 3.9.6
Hello Mark.
Feel free to let me know if your situation is as follows:
-- forked build (i.e. not in process)
-- when disabling the fork and enabling "-e" or running the build with
javac directly outside of Maven, suddenly error messages appear at
the end of the build
-- optionally
You might as well use the '-e' flag too to show the stack trace. Possibly
consider updating the compiler-plugin version too (it's up to 3.12.0) if
you're using an old one?
Knowing the exception line number and your version of the compiler plugin
you might browse the source at the corresponding
Good guess. Turns out it doesn't though. I checked yesterday.
My latest theory is that it's running out of memory during compilation.
But that would presumably end up in the logs, so this theory has problems.
-Original Message-
From: Tomo Suzuki
Sent: Tuesday, December 19, 2023 6:15
My guess is that your Maven project uses failOnWarning.
https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#failOnWarning
On Tue, Dec 19, 2023 at 5:38 PM Thomas Broyer wrote:
> In `mvn -X` you should find the arguments to javac (beware that empty
> arguments are not
In `mvn -X` you should find the arguments to javac (beware that empty
arguments are not displayed there, rather than being shown as "" for
instance), which would allow you to run javac on your own, taking Maven out
of the equation.
Le mar. 19 déc. 2023, 23:28, a
écrit :
> Indeed, if there were
That last part sounds promising actually! Sadly I'm not familiar with the
maven source code but still the ability to set breakpoints sounds very tempting!
-Original Message-
From: Mark Eggers
Sent: Tuesday, December 19, 2023 5:33 PM
To: users@maven.apache.org
Subject: Re: maven
I think the first two will help you compare what's working to what's not
working.
The -X does generate a LOT of output. Use -l [filename] to catch it.
When you start reading it, you'll be able to ignore a lot of the chatter.
You can also set slf4j logging options on the command line to help
Indeed, if there were ACTUAL error messages from the java compiler, this would
be far less mysterious :)
The trouble is that there are NOT any error messages coming from the Java
compiler.
There are a few warnings (from javac), followed soon after by "Compilation
failure" (from maven, NOT from
What’s the exact error messages?
(Maybe I’m too old to feel your pain) If you use Java, you need to know
what compilation means (converting Java code to Java bytecode). Your Maven
invocation was telling it was failing due to some error messages.
On Tue, Dec 19, 2023 at 16:57 wrote:
> When my
Thanks, I've heard of all three; the first two don't seem like they'd help here.
The third tends to spew junk and not useful stuff
-Original Message-
From: Mark Eggers
Sent: Tuesday, December 19, 2023 5:11 PM
To: users@maven.apache.org
Subject: Re: maven debugging frustrations
Some commands that might help you get started:
What are you using to build the artifact
mvn help:effective-pom
mvn help:effective-pom -Dverbose
What artifacts are being brought in
--
mvn
When my Java code does something I didn't expect, I can run it under a debugger
and step through it line by line until things make sense again.
When maven does something I didn't expect, my debugging strategy is usually
more like "try to think of something in my bag of tricks".
Sometimes I
I'll have to think about how this works and the ramifications. Off the
top of my head, I'm not sure how packaging the artifact as a JAR would help.
We make use of overlays, and then override the content in the project
that depends on the WAR by utilizing Maven's WAR overlays. Basically,
the
Thank you! I'd seen [4] but not sure if I've seen [2]
-Original Message-
From: Maarten Mulders
Sent: Tuesday, December 19, 2023 9:07 AM
To: users@maven.apache.org
Subject: Re: Maven 4.0 release timeline
CAUTION: This email originated from outside our organisation -
On 18/12/2023 21:38, mark.yagnatin...@barclays.com.INVALID wrote:
I'm not the original asker but this kind of answer tends to annoy me.
Yes, there is no "official" release timeline, you're obviously not going to
promise anything, all this is (hopefully?) clear, BUT!
You no doubt have GUESSES.
Gary,
you obviously did not read my message carefully. Please read one more
time. You will find out, that I did not call Maven's position ridiculous
*at all*, but on the contrary agreed with it, calling it a totally
valid statement.
What I called and am still calling ridiculous, is the wrong
As a fly on the wall here, not a dev, I think a kinder view would
reinterpret Maven's position not as "ridiculous" but rather
"down-priority", as in "we are busy, we like fixing bugs, adding features,
and scheduling things is not as important, otherwise this would turn into a
real job ;-)"
Gary
Can’t these resources be packaged in plain JARs and added as a regular
dependency to the applications that require them, instead of using WAR overlays?
Nils.
> Op 19 dec 2023, om 06:53 heeft Mark Eggers
> het volgende geschreven:
>
> I have several artifacts that consist of WAR archives with
19 matches
Mail list logo
