Okay, I think I got it. Here is the error I get when running with -J-Xmx800 <snip warnings about using internal APIs> The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: GC overhead limit exceeded <snip long stack trace from the depths of javac>
-----Original Message----- From: mark.yagnatin...@barclays.com.INVALID <mark.yagnatin...@barclays.com.INVALID> Sent: Friday, December 22, 2023 9:45 AM To: users@maven.apache.org Subject: RE: maven debugging frustrations CAUTION: This email originated from outside our organisation - mark.yagnatin...@barclays.com.INVALID Do not click on links, open attachments, or respond unless you recognize the sender and can validate the content is safe. How can I can find out EXACTLY how maven invoked javac, so I can invoke it the same way? (While I await your response, I'll attempt to invoke it roughly the same way and see if that works.) -----Original Message----- From: Alexander Kriegisch <alexan...@kriegisch.name> Sent: Thursday, December 21, 2023 8:45 PM To: users@maven.apache.org Subject: Re: maven debugging frustrations CAUTION: This email originated from outside our organisation - alexan...@kriegisch.name Do not click on links, open attachments, or respond unless you recognize the sender and can validate the content is safe. Mark, you asked for help here, now I am asking for your help to make Maven Compiler and Maven Plexus Java better. Can you please switch back to the too-low memory settings you used before and reproduce the javac error output when compiled outside Maven? Was it something as simple as: $ javac -J-Xmx32k org/example/MySecondAnnotation.java Error occurred during initialization of VM Initial heap size set to a larger value than the maximum heap size This would be silently swallowed even after my fix, because my fix was about stack trace parsing. It is, however, much more difficult to separate other JVM or javac error output from output possibly produced by e.g. annotation processors. It does not get easier, given the fact, that JVM output is localised to a handful of languages, not just English. Or did you get some kind of out of memory error with a stack trace? The error parser for forked javac undoubtedly needs more hardening and improvements to at least parse (and display!) the most common error messages correctly. I scratched my own itch lately by contributing an improvement for the first time. Before I forget about the source code context again and move on to other projects, maybe I can contribute a little bit more. But then, I need input. Thanks in advance and kind regards -- Alexander Kriegisch https://clicktime.symantec.com/15siQqy2D74kaQgWiyWS2?h=K9eKgEK3KMNDQERT1qp6hASj2Lxz71_qkmqF5v0_ueU=&u=https://clicktime.symantec.com/15t64tYyoA1WdgmTZsmn2?h=I98HUPo0DHKTqOkdZ1TN4skRFZCJraqV71xYi96Hcs0=&u=https://scrum-master.de mark.yagnatin...@barclays.com.INVALID schrieb am 21.12.2023 23:43 (GMT +07:00): > Forked: yes > Other questions: didn't check, because using a bigger heap ("maxmem") fixed > it. > But thanks for this, that looks like it would have helped us! > (in a hypothetical world where that PR was merged ten years earlier) > (We're mostly using version 3.8 of maven-compiler-plugin...perhaps > it's time to > upgrade.) > > -----Original Message----- > From: Alexander Kriegisch <alexan...@kriegisch.name> > Sent: Wednesday, December 20, 2023 12:41 AM > To: users@maven.apache.org > Subject: Re: maven debugging frustrations > > > CAUTION: This email originated from outside our organisation - > alexan...@kriegisch.name Do not click on links, open attachments, or > respond unless you recognize the sender and can validate the content is safe. > 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 (not necessarily) using a JDK locale other than English > (e.g. javac in JDK 21 comes with localised messages in Chinese, > Japanese, German) > -- optionally (not necessarily) using an annotation processor > > I recently had the symptom of build errors with forked compiler > swallowing error messages and scratched my own itch by adding a PR to > Plexus Javac which for me solves the problem. If your problem happens > to be the same category, you would be the perfect sentient test > particle for > https://clicktime.symantec.com/15t5ejaZW5bYZxdqr5n2v?h=L374vY2E9JSjErAq9vkYZyMzPS76MKSF_SWNxb51rVE=&u=https://clicktime.symantec.com/15siFBZrUArbTHh6FWx5d?h%3D_vziVdl8fIA-_du7fPQDmEDaVPK6D7XlieIqn88Lnv0%3D%26u%3Dhttps://clicktime.symantec.com/15siL1mjkVPAATrbBR7HQ?h%3DsoRGieRSYIcaVDaMRpuEKiTr-X0PEnOQaKTTUdxCkog%3D%26u%3Dhttps://github.com/codehaus-plexus/plexus-compiler/pull/337. > I can advise you how to get that running in your project. > > Regards > -- > Alexander Kriegisch > https://clicktime.symantec.com/15t5jZmqxhH8yuTmPeBBY?h=wp1fqXetHhmLNKfUOtcHtbgzJiXdEB-XVpPIvdPgMYY=&u=https://clicktime.symantec.com/15siL1m8vnYBsEX1o5MEF?h%3DEIrFDp-q7MAJaGl > zS3rT2Qpp_OrLzsXNXIASmesIlO4=&u=https://clicktime.symantec.com/15t5pPy8RJxjPrHgwCaLA?h=_lizuUKfsYIKAcM-Pa5yTH6dfcc0ASbjc7Bu0Yq5xFI=&u=https://clicktime.symantec.com/15siQqy > 2D74kaQgWiyWS2?h=K9eKgEK3KMNDQERT1qp6hASj2Lxz71_qkmqF5v0_ueU=&u=https: > //scrum-master.de > > > mark.yagnatin...@barclays.com.INVALID schrieb am 20.12.2023 05:27 (GMT > +07:00): > >> 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) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > 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/15sipzwSWBUie8p8SmWB8?h=m9dLh07WmQWDXYFhNfP3-MeGqwAfIhIFQONPqavCBec=&u=https://clicktime.symantec.com/15t6ehuy1TnfXJYvNnZpN?h=QzW1apxwezrSGejb1l1PGq2fJ2VEqwnONpg-dZ37YVc=&u=https://www.cib.barclays/disclosures/web-and-email-disclaimer.html. > > > For important disclosures, please see: > https://clicktime.symantec.com/15t5z4MhLYKvDjwY2KNdQ?h=yqMI_xjzeoTF230ONAhuWrftiBjys4386zqGrTjw1PA=&u=https://clicktime.symantec.com/15sikAkA3Zo8EBzCuD72W?h%3D9fijqSv-cP3_fLA > 82P9yVnpQaI-jKXIW3Iw9ROJlRkk=&u=https://clicktime.symantec.com/15t6V3XQ6ERUhQu5HfmX8?h=rAaU8vCFkrVHfEqzb_wmaJLeQjEQoWzgQ-3U4Swv0ZQ=&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/15t5uEAQsveKoo7cUkyUn?h=yADx6WHIr_-zqEeX6f1LbAsyBuLaR-Ra5bFYCDKetpk=&u=https://clicktime.symantec.com/15siVgAJfikLzMWSGXuae?h%3DBVIRBfgjMqAle6X > 4PoJKt1ITWBJCizki-XZO_1mQ2p4=&u=https://clicktime.symantec.com/15t69ikGFmh73dbP7SAve?h=tyAGurgq1be6qEqRXBMd9d9Y_0_uzDmNfcan5mHrMW8=&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/15siFBaTHshZkX2fdri8n?h=r3kePnO0t7DFPXH05AU8SECF75SujMUzaS9_NwhNDrI=&u=https://clicktime.symantec.com/15t5ZuPH3TuxA1ovJXNtJ?h=1odndS_eh597rXzn00qaTvcBJKgr5egFitu-w1Q-Sd4=&u=http://publicresearch.barclays.com. > ______________________________________________________________________ > ____________ > > If you are incorporated or operating in Australia, read these > important > disclosures: > https://clicktime.symantec.com/15siaWMb8LRwQJLMp6JjG?h=SYXtLFMlFZd9kA48wZugsd0Vajkhgo_5gxltfdkDC0c=&u=https://clicktime.symantec.com/15t6KP8qB14HsXFECYyDt?h=h1a_P3i8FG2868jYls8uEwnQiAcku_VeerPYe_dIydw=&u=https://www.cib.barclays/disclosures/important-disclosures-asia-pacific.html. > ______________________________________________________________________ > ____________ For more details about how we use personal information, > see our privacy notice: > https://clicktime.symantec.com/15sifLYsax7XpFAHMehst?h=s142BIKT_WRDjnuMhLSwVbzKbLJQLWoRw8qCThtaDf0=&u=https://clicktime.symantec.com/15t6QDL7dcjtHU59k7NNW?h=0Frf5nePg4q4ZQE-5xAJ8OXPcfiBTiTVWI8VaZx4F5g=&u=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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org 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/15t6ehuy1TnfXJYvNnZpN?h=QzW1apxwezrSGejb1l1PGq2fJ2VEqwnONpg-dZ37YVc=&u=https://www.cib.barclays/disclosures/web-and-email-disclaimer.html. For important disclosures, please see: https://clicktime.symantec.com/15t6ZsigYr757MizqEAfk?h=SwkoyvDXuTIOe8fqGe8GvC2VJj_MuT4hd6193Fkorf4=&u=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://clicktime.symantec.com/15t6EYwYiPNhTaRJeza5G?h=iKqKjCj9mx2d5L840ghrI9ELFz5KHeK4lKcjepanrDU=&u=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: https://clicktime.symantec.com/15t5ZuPH3TuxA1ovJXNtJ?h=1odndS_eh597rXzn00qaTvcBJKgr5egFitu-w1Q-Sd4=&u=http://publicresearch.barclays.com. __________________________________________________________________________________ If you are incorporated or operating in Australia, read these important disclosures: https://clicktime.symantec.com/15t6KP8qB14HsXFECYyDt?h=h1a_P3i8FG2868jYls8uEwnQiAcku_VeerPYe_dIydw=&u=https://www.cib.barclays/disclosures/important-disclosures-asia-pacific.html. __________________________________________________________________________________ For more details about how we use personal information, see our privacy notice: https://clicktime.symantec.com/15t6QDL7dcjtHU59k7NNW?h=0Frf5nePg4q4ZQE-5xAJ8OXPcfiBTiTVWI8VaZx4F5g=&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. __________________________________________________________________________________
