On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> I just fixed a few failing jobs [1] to have again a usable Jenkins. > > Now I'm facing some issues, I suppose caused by newer Jenkins versions: > - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.MXParser > [2] > - I had to switch to JDK 8 for maven-plugin-tools job, since JDK causes > failures (looks like Jenkins uses a hack to inject JDK 7 as a tool while > the > build JVM is Java 8) > > Should we drop Maven 3.0.5 builds and JDK 7? > Notice I didn't check which is the minimum Maven version required... > > Or perhaps simply don't use the Jenkins Maven plugin with this Maven 3.0.5 > or > JDK 7 configuration: default build as Jenkins Maven plugin with JDK 8 + > latest > Maven, and other configurations as scripted jobs? http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html <http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html?m=1> We should stop using the evil job type as it’s minimum Java version is dictated by Jenkins’ Java minimum. > > We need to define our common strategy and have a consistent configuration > for > every job understood by everybody I recommend Jenkinsfile and the `withMaven` wrapper > > > Regards, > > Hervé > > [1] https://builds.apache.org/view/M-R/view/Maven/ > > [2] > https://builds.apache.org/view/M-R/view/Maven/job/maven-plugin-tools-jdk-1.7/162/console > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
