Maven 4.0 (RC3) causes Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.1:exec

[vorburger]

Please provide:

• Link to build log from https://jitpack.io

https://jitpack.io/com/github/enola-dev/adk-java/LangChain4j-preview-b0c4a94e99-1/build.log

• Does the project build on your machine with the same commands as in the log (e.g. ./gradlew install) ?

Yes.

• What error are you seeing?

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Google Agent Development Kit Maven Parent POM 0.1.1-SNAPSHOT:
[INFO] 
[INFO] Google Agent Development Kit Maven Parent POM ...... SUCCESS [  1.176 s]
[INFO] Agent Development Kit .............................. SUCCESS [ 26.028 s]
[INFO] Agent Development Kit - Dev Tools .................. SUCCESS [  3.486 s]
[INFO] Agent Development Kit - LangChain4j Integration .... SUCCESS [  1.427 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  52.141 s
[INFO] Finished at: 2025-06-06T19:48:46Z
[INFO] ------------------------------------------------------------------------
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.3.1:exec (default-cli) on project google-adk-parent: Execution default-cli of goal org.codehaus.mojo:exec-maven-plugin:1.3.1:exec failed: Cannot invoke "org.codehaus.plexus.PlexusContainer.lookup(String)" because the return value of "org.apache.maven.execution.MavenSession.getContainer()" is null -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the '-e' switch
[ERROR] Re-run Maven using the '-X' switch to enable verbose output
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
Build tool exit code: 0

This appears to be causing by https://github.com/enola-dev/adk-java/tree/b0c4a94e99f4554bae30541351839b4da4b6dbbf using Maven 4.0.0 (RC3) [here], and goes away at https://github.com/enola-dev/adk-java/tree/41254a8f39e957b4f9b5277763bb6afb67419d5e after https://github.com/enola-dev/adk-java/commit/41254a8f39e957b4f9b5277763bb6afb67419d5e which downgrades to Maven 3.9.10, where on https://jitpack.io/com/github/enola-dev/adk-java/LangChain4j-preview-41254a8f39-1/build.log it is:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Google Agent Development Kit Maven Parent POM 0.1.1-SNAPSHOT:
[INFO] 
[INFO] Google Agent Development Kit Maven Parent POM ...... SUCCESS [  0.669 s]
[INFO] Agent Development Kit .............................. SUCCESS [ 18.283 s]
[INFO] Agent Development Kit - Dev Tools .................. SUCCESS [  2.805 s]
[INFO] Agent Development Kit - LangChain4j Integration .... SUCCESS [  0.946 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  37.344 s
[INFO] Finished at: 2025-06-06T22:16:47Z
[INFO] ------------------------------------------------------------------------
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
Found module: com.google.adk:google-adk-parent:0.1.1-SNAPSHOT
Found module: com.google.adk:google-adk:0.1.1-SNAPSHOT
Found module: com.google.adk:google-adk-dev:0.1.1-SNAPSHOT
Found module: com.google.adk:google-adk-langchain4j:0.1.1-SNAPSHOT
Build tool exit code: 0
Looking for artifacts...
Looking for pom.xml in build directory and ~/.m2
Found artifact: com.google.adk:google-adk-parent:0.1.1-SNAPSHOT
Found artifact: com.google.adk:google-adk-langchain4j:0.1.1-SNAPSHOT
2025-06-06T22:16:51.635690595Z
Exit code: 0

@glaforge FYI

Thank you!

[cstamas]

This is not jitpack issue, you are using old exec plugin: https://github.com/mojohaus/exec-maven-plugin/issues/401

Upgrade exec-maven-plugin to 3.2.0+ (just go for latest: 3.5.1) https://github.com/mojohaus/exec-maven-plugin/releases/tag/3.2.0 https://github.com/mojohaus/exec-maven-plugin/releases/tag/3.5.1

[vorburger]

To clarify, the you (in "you are using old exec plugin") is NOT the project being built (which does not actually use the exec-maven-plugin),

BUT the JitPack "platform", which on its own appears to run the org.codehaus.mojo:exec-maven-plugin:1.3.1:exec after builds, presumably for something internal to JitPack.

So the ask here is to upgrade JitPack's use of an ancient (1.3.1) version of the exec-maven-plugin.

[cstamas]

Oh, if that is the case, it would be "very nice" of them to use latest (bugfixed, etc) version. Sorry for confusion, I assumed your POM defines some ancient exec plugin version...

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.