-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
jenkins 2.232
java 11.0.3 [AdoptOpenJDK (build 11.0.3+7)]
maven 3.6.3
as discussed with Olivier Lamy in maven mailing list thread here a standard maven job does not take core-extensions into consideration.
Detailled instructions to reproduce can be found in the thread.
Perhaps related to https://issues.jenkins-ci.org/browse/JENKINS-40621
olamy I'm working to make Gradle Enterprise compatible with the Maven job type in Jenkins. GE for Maven is implemented as a Maven Extension, and our customers currently have to migrate away from using the `maven-plugin` to benefit from caching and build scans.
Do you have any hints/advice on where I would start to make Maven detect and load extensions declared in the project `.mvn` directory?
I added `-Dmaven.multiModuleProjectDirectory=...` and `-Dmaven.projectBasedir=...` to the invocation, but that didn't seem to help.