Remove `<mavenExecutorId>forked-path</mavenExecutorId>`?
basil opened this issue · 0 comments
basil commented
We don't customize this in jenkinsci/pom, and automated release of both Jenkins core and core components seem to work fine without it, as do manual releases with maven-release-plugin. Seems more straightforward to me to get rid of this customization and follow a more standard code path that is in line with Maven defaults. I was unable to find any commit messages or tickets that explain the reason why this was customized to begin with.