Disclaimer: This drops support of any spring version that does not have a bootJar task, mainly spring v1
Adjust the JavaProvider so that it uses bootJar to build an executable JAR instead of build which generates a *plain.jar also when spring and gradle is detected
Add e2e test cases for spring v2 and v3, also remove spring v1
Update the docs of the JavaProvider so that it has information regarding the spring version support, and the build commands
As per the comments below PR implements a different solution now:
Adjust the JavaProvider so that if gradle and spring is detected then the start cmd includes a one line to find the executable jar and blacklists the plain.jar
Add e2e test cases for spring v1, v2 and v3
Update the docs of the JavaProvider so that it includes description for the new start cmd if gradle and spring is detected
coffee-cup
commented
10 months ago
This PR solves the following issue: https://github.com/railwayapp/nixpacks/issues/979
Disclaimer: This drops support of any spring version that does not have abootJartask, mainly spring v1Adjust theJavaProviderso that it usesbootJarto build an executable JAR instead ofbuildwhich generates a*plain.jaralso when spring and gradle is detectedAdd e2e test cases for spring v2 and v3, also remove spring v1Update the docs of theJavaProviderso that it has information regarding the spring version support, and the build commandsAs per the comments below PR implements a different solution now:
JavaProviderso that if gradle and spring is detected then the start cmd includes a one line to find the executable jar and blacklists the plain.jarJavaProviderso that it includes description for the new start cmd if gradle and spring is detected