Maven Buildpack fails with code 145 about java

[pax95]

Ahh now it's getting clear to me. The buildpack sees a mvnw script in the project and uses that to run/download maven. This script has not been updated since we run vanilla maven locally. Updating the script or removing it will properly solve the issue.

[pax95]

Realized that this possibly should have been raised here https://github.com/paketo-buildpacks/maven

You get the same output when running ❯ pack build foo --builder paketobuildpacks/builder:base on a maven based java 11 project

[dmikusa]

The suggested solution here would be to use a newer version of Maven. The flag mentioned in the error, --no-transfer-progress is from Maven 3.6.1 (2019). You should use a version of Maven newer than that.

By default, the buildpack will install a version of Maven that is newer than 3.6.1 and compatible with this argument. However, if you are using Maven Wrapper, then the version of Maven is dictated by the Maven wrapper present in your application. You likely need to update your Maven wrapper so it's using a newer version. Then next time you build, the buildpack will use that version of Maven.

If you cannot update Maven for some reason, set the env variable BP_MAVEN_BUILD_ARGUMENTS to -Dmaven.test.skip=true package with pack build -e BP_MAVEN_BUILD_ARGUMENTS='-Dmaven.test.skip=true package'. That will override the default set of Maven arguments and remove the one incompatible with your older version of Maven.

[pax95]

The project is not using any wrapper and will rely on the maven buildpack for taking action on installing the correct maven version. I have verified that this is happening on a java 17 project, but not when java 11 project ??
Here is the output from the java 17 project where maven is contributing ->
Paketo Maven Buildpack 6.5.0
https://github.com/paketo-buildpacks/maven
Build Configuration:
$BP_MAVEN_BUILD_ARGUMENTS -Dmaven.test.skip=true --no-transfer-progress package the arguments to pass to Maven
$BP_MAVEN_BUILT_ARTIFACT target/*.[ejw]ar the built application artifact explicitly. Supersedes $BP_MAVEN_BUILT_MODULE
$BP_MAVEN_BUILT_MODULE the module to find application artifact in
$BP_MAVEN_DAEMON_ENABLED false use maven daemon
$BP_MAVEN_POM_FILE pom.xml the location of the main pom.xml file, relative to the application root
Apache Maven 3.8.5: Contributing to layer
Downloading from https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.8.5/apache-maven-3.8.5-bin.tar.gz
Verifying checksum
Expanding to /layers/paketo-buildpacks_maven/maven
Creating cache directory /home/cnb/.m2

I think this i a bug in the builder, and that I know that i can temporary fix this by overriding the MAVEN_BUILD_ARGUEMENTS as stated.

[dmikusa]

Executing mvnw --batch-mode -Dmaven.test.skip=true --no-transfer-progress package

In your original post, it says mvnw ^^^. Are you certain?

I can take a closer look if you include the full output from building, as well as the full pack buildcommand you're running. It's hard to say what might be happening without the full output. Or if you can include a sample project, I can try to reproduce it on my end. Thanks

[pax95]

Closing this now. Thanks for pointing me in the right direction :-)

[dmikusa]

No problem, happy to help.