Re: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist
Thu, 21 Dec 2023 09:10:44 +0100, /Slawomir Jaranowski/: Release under vote ... you can check candidate version: https://lists.apache.org/thread/scb8qw1or396l4hqgf5h78z5h0km60z4 Tried maven-compiler-plugin 3.12.1 from the staging repository – no error during the build. -- Stanimir - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist
Hi, Release under vote ... you can check candidate version: https://lists.apache.org/thread/scb8qw1or396l4hqgf5h78z5h0km60z4 śr., 20 gru 2023 o 21:04 Slawomir Jaranowski napisał(a): > Hi > > MCOMPILER-379 - was about missing SourcesDirectory and we have IT for it: > https://github.com/apache/maven-compiler-plugin/commit/6fd3a46885edd81e62ae62cfc798c1e1b903e170 > > MCOMPILER-567 - is for missing generated-sources/annotations - now we also > have IT for it: https://github.com/apache/maven-compiler-plugin/pull/218 > > Additionally I add a check in plexus-compiler > https://github.com/codehaus-plexus/plexus-compiler/pull/338 > > So we should be safe with mentioned fixes. > > > śr., 20 gru 2023 o 20:43 Greg Chabala napisał(a): > >> Hello Sławomir, >> >> Do you know if MCOMPILER-379 is the same issue as MCOMPILER-567 ? If so, >> shouldn't the IT test in MCOMPILER-379 have caught it? >> >> Greg >> > > > -- > Sławomir Jaranowski > -- Sławomir Jaranowski
Re: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist
Hi MCOMPILER-379 - was about missing SourcesDirectory and we have IT for it: https://github.com/apache/maven-compiler-plugin/commit/6fd3a46885edd81e62ae62cfc798c1e1b903e170 MCOMPILER-567 - is for missing generated-sources/annotations - now we also have IT for it: https://github.com/apache/maven-compiler-plugin/pull/218 Additionally I add a check in plexus-compiler https://github.com/codehaus-plexus/plexus-compiler/pull/338 So we should be safe with mentioned fixes. śr., 20 gru 2023 o 20:43 Greg Chabala napisał(a): > Hello Sławomir, > > Do you know if MCOMPILER-379 is the same issue as MCOMPILER-567 ? If so, > shouldn't the IT test in MCOMPILER-379 have caught it? > > Greg > -- Sławomir Jaranowski
Re: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist
Hello Sławomir, Do you know if MCOMPILER-379 is the same issue as MCOMPILER-567 ? If so, shouldn't the IT test in MCOMPILER-379 have caught it? Greg
RE: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist
Hi, I faced the similar error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.12.0:testCompile (default-testCompile) Fatal error compiling: basedir ...\target\generated-test-sources\test-annotations-java does not exist -> [Help 1] and investigating I see it is not on all projects but only on these where the message [INFO] --- maven-compiler-plugin:3.12.0:testCompile (default-testCompile) @ ... --- [INFO] Recompiling the module because of changed dependency. above is printed. Workaround for me was to add false to the maven-compiler-plugin-configuration. Now same build prints [INFO] --- maven-compiler-plugin:3.12.0:testCompile (default-testCompile) @ ... --- [INFO] Nothing to compile - all classes are up to date. and no error comes up. Gruß, Stefan -Original Message- From: Slawomir Jaranowski Sent: Wednesday, December 20, 2023 9:41 AM To: Maven Users List Subject: Re: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist Hi, Thanks for the report .. We are working on it, the new release should be in a few days. https://issues.apache.org/jira/browse/MCOMPILER-567 śr., 20 gru 2023 o 08:09 Stanimir Stamenkov napisał(a): > 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 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: ...\apache-maven-3.9.6 > Java version: 21.0.1, vendor: Eclipse Adoptium, runtime: ...\jdk-21 > Default locale: en_US, platform encoding: UTF-8 > OS name: "windows 10", version: "10.0", arch: "amd64", family: > "windows" > ... > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile > (java9-compile) on project xbrz-core: Fatal error compiling: basedir > C:\...\xbrz-java\xbrz-core\target\generated-sources\annotations does > not exist -> [Help 1] > > that doesn't occur with the compiler plugin 3.11.0. The local change > that appears to trigger the error with the compiler plugin 3.12.0 is > I've deleted "module-info.java" sources: > > del /s module-info.java # or with bash > > find -name module-info.java -print -delete > > Funny enough, if I restore "xbrz-core/src/main/java9/module-info.java" > both of "xbrz-core" and "xbrz-awt" get built successfully, then > "xbrz-tool" fails the same. > > Does this behavior appear a regression? I've found a similar symptom > fixed long time ago: > > * https://issues.apache.org/jira/browse/MCOMPILER-379 > > [1] https://lists.apache.org/thread/9x7p7k5n7vptopqrt55o7c2pg7pnznh2 > [2] https://github.com/stanio/xbrz-java > > Note, "xbrz-java" currently requires JDK 21 for building just for > the javadoc generation. One may edit .mvn/enforcer-extension.xml to > relax this requirement for the purpose of `mvn package` alone. > > -- > Stanimir > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Sławomir Jaranowski C Services GmbH & Co. OHG | Wanheimer Straße 70 | D-40468 Düsseldorf | Sitz: Düsseldorf | Registergericht: Düsseldorf HRA 12655 | Telefon: +49 (211) 9872-01 Persönlich haftende Gesellschafter: C Retail GmbH | Sitz: Baar/Schweiz | UID: CHE-116.290.471 Geschäftsführung: Giny Boer, Christoph Hammer FRM Participations S.A. | Sitz: Strassen/Luxemburg | Handels- und Firmenregister Luxemburg: B 58158 Verwaltungsratsmitglieder: Dr. Christian Bank, Remco Gerlof, Dr. Franz-Josef Leuchtenberg Hinweise zur Verarbeitung Ihrer Daten finden Sie unter: www.c-a.com/GDPR<http://www.c-a.com/GDPR> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist
Hi, Thanks for the report .. We are working on it, the new release should be in a few days. https://issues.apache.org/jira/browse/MCOMPILER-567 śr., 20 gru 2023 o 08:09 Stanimir Stamenkov napisał(a): > 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 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: ...\apache-maven-3.9.6 > Java version: 21.0.1, vendor: Eclipse Adoptium, runtime: ...\jdk-21 > Default locale: en_US, platform encoding: UTF-8 > OS name: "windows 10", version: "10.0", arch: "amd64", family: > "windows" > ... > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile > (java9-compile) on project xbrz-core: Fatal error compiling: basedir > C:\...\xbrz-java\xbrz-core\target\generated-sources\annotations does not > exist -> [Help 1] > > that doesn't occur with the compiler plugin 3.11.0. The local change > that appears to trigger the error with the compiler plugin 3.12.0 is > I've deleted "module-info.java" sources: > > del /s module-info.java # or with bash > > find -name module-info.java -print -delete > > Funny enough, if I restore "xbrz-core/src/main/java9/module-info.java" > both of "xbrz-core" and "xbrz-awt" get built successfully, then > "xbrz-tool" fails the same. > > Does this behavior appear a regression? I've found a similar symptom > fixed long time ago: > > * https://issues.apache.org/jira/browse/MCOMPILER-379 > > [1] https://lists.apache.org/thread/9x7p7k5n7vptopqrt55o7c2pg7pnznh2 > [2] https://github.com/stanio/xbrz-java > > Note, "xbrz-java" currently requires JDK 21 for building just for > the javadoc generation. One may edit .mvn/enforcer-extension.xml to > relax this requirement for the purpose of `mvn package` alone. > > -- > Stanimir > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Sławomir Jaranowski
Fatal error compiling: basedir .../target/generated-sources/annotations does not exist
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 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) Maven home: ...\apache-maven-3.9.6 Java version: 21.0.1, vendor: Eclipse Adoptium, runtime: ...\jdk-21 Default locale: en_US, platform encoding: UTF-8 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" ... [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile (java9-compile) on project xbrz-core: Fatal error compiling: basedir C:\...\xbrz-java\xbrz-core\target\generated-sources\annotations does not exist -> [Help 1] that doesn't occur with the compiler plugin 3.11.0. The local change that appears to trigger the error with the compiler plugin 3.12.0 is I've deleted "module-info.java" sources: del /s module-info.java # or with bash find -name module-info.java -print -delete Funny enough, if I restore "xbrz-core/src/main/java9/module-info.java" both of "xbrz-core" and "xbrz-awt" get built successfully, then "xbrz-tool" fails the same. Does this behavior appear a regression? I've found a similar symptom fixed long time ago: * https://issues.apache.org/jira/browse/MCOMPILER-379 [1] https://lists.apache.org/thread/9x7p7k5n7vptopqrt55o7c2pg7pnznh2 [2] https://github.com/stanio/xbrz-java Note, "xbrz-java" currently requires JDK 21 for building just for the javadoc generation. One may edit .mvn/enforcer-extension.xml to relax this requirement for the purpose of `mvn package` alone. -- Stanimir - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
