Démarré à distance par l'hôte 140.82.115.122140.82.115.122Started by GitHub push by mmoqui2975b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/master5b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/master5b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git297f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom297a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom2975a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/master5a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/master5a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2608203983838064Silverpeas_Project_Definition_AutoDeploy 2.0-build260820297false29758103SUCCESS1787231155896https://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/297/pom.xmla099b59d24d9b52a26274503c77c74076a7475f21787231024000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comDrop junit-platform-runner and align the JUnit Platform on the junit-bom Surefire 3.x disables its JUnit Platform provider as soon as junit-platform-runner is on the test classpath: that runner exists to drive the platform from the JUnit 4 provider. The result is that every Jupiter test is silently ignored (only the JUnit 4 ones still run) with no warning at all. No source uses @RunWith(JUnitPlatform.class), so the dependency is dead weight. Importing the junit-bom keeps commons, engine and launcher on the same version; the launcher used to lag 1.9.2 behind engines in 1.11.4. 2026-08-20 15:03:44 +0200a099b59d24d9b52a26274503c77c74076a7475f2Drop junit-platform-runner and align the JUnit Platform on the junit-bomeditpom.xmlgitpom.xml877d33c4a792883d3c20fbc9b60e73eca92fa8361787229899000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpgrade the build toolchain to support Java 21 Java 21 requires newer versions of several plugins: - jacoco 0.8.8 only knows class files up to Java 17 (major 61) and fails on major 65; 0.8.11 is the first release supporting Java 21. - surefire/failsafe 2.22.2 predate JDK 21 and are no longer tested against it. - maven-compiler-plugin 3.10.1 and Maven 3.6.3 both predate JDK 17 support. Drop the maven-taglib plugin, which Jakarta EE made unusable Its last release, 2.4, dates back to January 2010 and only knows the http://java.sun.com/xml/ns/javaee namespace and the javax.servlet.jsp.tagext classes. Our TLDs moved to https://jakarta.ee/xml/ns/jakartaee and our tags to jakarta.servlet.jsp, so the taglibdoc report errors out and the validate report fails the whole site build on a null tagSupportClass. No newer release exists and none is expected, so mvn site was simply broken. There is no replacement: the tag library reference is no longer generated. 2026-08-20 14:44:59 +0200877d33c4a792883d3c20fbc9b60e73eca92fa836Upgrade the build toolchain to support Java 21editpom.xmlpom.xmld05003e35aa083e1b4213e6b7858ffb308d9610d1787229961000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comMigrate some Maven plugins to another vendor: * pl.project13.maven:git-commit-id-plugin by io.github.git-commit-id:git-commit-id-maven-plugin 10.0.0 pl.project13.maven:git-commit-id-plugin is the abandoned coordinates of the plugin; 4.9.10 dates back to 2021 and cannot read a .git file, so it breaks on any git worktree. Version 10.0.0 requires Maven 3.9+, which the parent POM now declares as a prerequisite. The git.commit.id.abbrev property feeding the jar manifests is unchanged. * Miredot plugin by Smart-Doc to generate the REST API doc Use the still released com.github.shalousun coordinates of Smart-Doc. Smart-Doc is published under two groupIds. com.ly.smart-doc stops at 3.1.2, released in September 2025, whereas com.github.shalousun keeps being released and is now on 4.0.0 (July 2026). Pinning 3.1.0 to dodge the DocJavaMethod regression of 3.1.1 and 3.1.2 was therefore holding us on the dead line. Miredot is a discontinued product; its last build, 2.4.1-Java11, is pinned to Java 11 and was never exercised on Java 21. Smart-Doc reads the sources with qdox and ships a JAXRSDocBuildTemplate that knows the jakarta.ws.rs annotations, so it fits our Jakarta EE 10 resources. Version 3.1.0 is pinned on purpose: 3.1.1 and 3.1.2 regressed on the JAX-RS template and title every endpoint com.ly.doc.model.DocJavaMethod. Unlike Miredot, Smart-Doc is configured per module through a smart-doc.json file; a module without one is skipped with a warning, so only the modules holding REST resources need the file. 2026-08-20 14:46:01 +0200d05003e35aa083e1b4213e6b7858ffb308d9610dMigrate some Maven plugins to another vendor:editpom.xmlpom.xml5a370360b2c7d47ec2960e23ab68acc658633a821787230495000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comNow Silverpeas can be built and executed with Java 21, Silverpeas can now be deployed onto Wildfly 39.0.1 (the latest supporting Jakarta EE 10). The next versions of Wildfly are for Jakarta EE 11 by default but provides also an alternative for Jakarta EE 10 2026-08-20 14:54:55 +02005a370360b2c7d47ec2960e23ab68acc658633a82Now Silverpeas can be built and executed with Java 21, Silverpeas can now be deployed onto Wildfly 39.0.1 (the latest supporting Jakarta EE 10). The next versions of Wildfly are for Jakarta EE 11 by default but provides also an alternative for Jakarta EE 10editpom.xmlgithttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse298https://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/298/296https://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/296/