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 <t.bro...@gmail.com> wrote: > 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, <mark.yagnatin...@barclays.com.invalid> a > écrit : > > > 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 javac) > > I do not recommend feeling my maven-based pain :) > > But if you happen to know where to get some pain relief, I'd love to know > > > > -----Original Message----- > > From: Tomo Suzuki <suzt...@google.com.INVALID> > > Sent: Tuesday, December 19, 2023 5:18 PM > > To: Maven Users List <users@maven.apache.org> > > Subject: Re: maven debugging frustrations > > > > > > CAUTION: This email originated from outside our organisation - > > suzt...@google.com.INVALID Do not click on links, open attachments, or > > respond unless you recognize the sender and can validate the content is > > safe. > > 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 <mark.yagnatin...@barclays.com.invalid> > > wrote: > > > > > 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 suddenly have an epiphany and I realize "oh, it must have > > > broken because of that thing I changed". > > > But in the absence of epiphanies, I don't have any good ways to ask > > > maven to tell me what on earth is going on. > > > > > > Example from today: some is failing on our build server with > > > "Compilation failure". > > > Looking at the build log, there are no compiler errors in sight. > > > There are a few compiler warnings, and those seem to logged twice: > > > once at warning level, and then again at error level. > > > It only fails on SOME (not all) of our build configs, even though our > > > configs are pretty darn similar to each other. > > > > > > So I'm left flailing around more or less at random (try compiling on a > > > different server! Try copying the command line flags from the one > > > that work! Etc.) What I actually want is for maven to give me some > > > CRUMB of visibility into what on earth is going wrong. > > > > > > I don't even know what "Compilation failure" actually means. > > > Did some process exit with non-zero status? > > > Did the process fail to launch in the first place? > > > Maybe there is no extra process, and the compilation is taking place > > > in the same JVM that's running maven? > > > If so, what went wrong? Did an exception get thrown? Something else? > > > > > > You get the idea. > > > > > > > > > This message is for information purposes only. It is not a > > > recommendation, advice, offer or solicitation to buy or sell a product > > > or service, nor an official confirmation of any transaction. It is > > > directed at persons who are professionals and is intended for the > > > recipient(s) only. It is not directed at retail customers. This message > > is subject to the terms at: > > > > > > https://clicktime.symantec.com/15sifLYAwPjLHCtCgybKg?h=ANvnaYG630AR0f2GLplpUfGbAsle9xaoL2f-FF_ESsU=&u=https://www.cib.barclays/disclosures/web-and-email-disclaimer.html > > . > > > > > > For important disclosures, please see: > > > https://clicktime.symantec.com/15siaWLtUn3jsG4H9RCB4?h=M6FIGRVBH8G_LIh > > > m9t5V7SPthNcb5IVYLL7498zEnzg=&u=https://www.cib.barclays/disclosures/s > > > ales-and-trading-disclaimer.html regarding marketing commentary from > > > Barclays Sales and/or Trading desks, who are active market > > > participants; > > > https://clicktime.symantec.com/15siL1m36vzxdRaWWjzjC?h=G7ajSU4AyuCbxlw > > > vIlksn83RCALP2_zHmu0XbnqwDpE=&u=https://www.cib.barclays/disclosures/b > > > arclays-global-markets-disclosures.html > > > regarding our standard terms for Barclays Corporate and Investment > > > Bank where we trade with you in principal-to-principal wholesale > > > markets transactions; and in respect to Barclays Research, including > > > disclosures relating to specific issuers, see: > > > https://clicktime.symantec.com/15siFBZkeKKNDUkayBbaa?h=G2aTqP2GUKb-ZJb3VDe2qGDqjn4glmlwiYEU-U9Qp08=&u=http://publicresearch.barclays.com > > . > > > ______________________________________________________________________ > > > ____________ > > > > > > If you are incorporated or operating in Australia, read these > > > important > > > disclosures: > > > https://clicktime.symantec.com/15siQqxKZYgZ3NQS4JPsp?h=_wyBE5fSRVnrjCX > > > _RdiyqX2Tzqlr_fF2jEBUkk9zsjg=&u=https://www.cib.barclays/disclosures/i > > > mportant-disclosures-asia-pacific.html > > > . > > > > > > ______________________________________________________________________ > > > ____________ For more details about how we use personal information, > > > see our privacy > > > notice: > > > https://clicktime.symantec.com/15siVg9c2AN9TKEMbro2S?h=YTZNN6svma8VJfLaKz8L06dizNzYH3spp4UdRQF7gVo=&u=https://www.cib.barclays/disclosures/personal-information-use.html > > . > > > > > > > > > ______________________________________________________________________ > > > ____________ > > > > This message is for information purposes only. It is not a > recommendation, > > advice, offer or solicitation to buy or sell a product or service, nor an > > official confirmation of any transaction. It is directed at persons who > are > > professionals and is intended for the recipient(s) only. It is not > directed > > at retail customers. This message is subject to the terms at: > > https://www.cib.barclays/disclosures/web-and-email-disclaimer.html. > > > > For important disclosures, please see: > > https://www.cib.barclays/disclosures/sales-and-trading-disclaimer.html > > regarding marketing commentary from Barclays Sales and/or Trading desks, > > who are active market participants; > > > https://www.cib.barclays/disclosures/barclays-global-markets-disclosures.html > > regarding our standard terms for Barclays Corporate and Investment Bank > > where we trade with you in principal-to-principal wholesale markets > > transactions; and in respect to Barclays Research, including disclosures > > relating to specific issuers, see: http://publicresearch.barclays.com. > > > __________________________________________________________________________________ > > > > If you are incorporated or operating in Australia, read these important > > disclosures: > > > https://www.cib.barclays/disclosures/important-disclosures-asia-pacific.html > > . > > > > > __________________________________________________________________________________ > > For more details about how we use personal information, see our privacy > > notice: > https://www.cib.barclays/disclosures/personal-information-use.html. > > > > > > > __________________________________________________________________________________ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > -- Regards, Tomo
