https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/<p>Job to build and deploy automatically the projects that define together the common properties and dependencies for all of the Silverpeas projects.</p>
<p>The job is triggered at change in the Github repositories of the projects related by this job.</p>Silverpeas_Project_Definition_AutoDeploySilverpeas_Project_Definition_AutoDeploySilverpeas_Project_Definition_AutoDeploySilverpeas_Project_Definition_AutoDeployhttps://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/trueDémarré à distance par l'hôte 140.82.115.31140.82.115.31Started by GitHub push by mmoqui301b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git301f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom301a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom301c35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2609154067639009Silverpeas_Project_Definition_AutoDeploy 2.0-build260915301false30159674SUCCESS1789482429565https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/301/- src/releases/silverpeas/Jenkinsfilesrc/builds/silverpeas/Jenkinsfile7e3556671c10e320bbd1de57e3638d1b427e63131788341397000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comFor the pipelines dedicated to build a build version of Silverpeas and
to release a stable version of Silverpeas (from a build version), mount
in the Docker container the file ~/.gradle/gradle.properties
configuration file in which should be defined the credentials for
publishing artefacts into our Maven/Gradle repo.
2026-09-02 11:29:57 +02007e3556671c10e320bbd1de57e3638d1b427e6313For the pipelines dedicated to build a build version of Silverpeas andeditsrc/releases/silverpeas/Jenkinsfileeditsrc/builds/silverpeas/Jenkinsfile
- src/releases/docker-build/Jenkinsfileb3a0a7bf423a3407c3bc6980f30a0c6ee678b5ae1788354644000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comNow by default Java version is 21 in the pipeline for building the project build Docker image
2026-09-02 15:10:44 +0200b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeNow by default Java version is 21 in the pipeline for building the project build Docker imageeditsrc/releases/docker-build/Jenkinsfile
git- pom.xmlc35c3985f86f4b10ff2dc6b681fce9d45575a3c81789482380000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comManage the tooling generating the documentation of the REST API
Smart-Doc is unable to document our REST API in a reliable way: it fails on
constructs we rely on, and reports a success while producing an incomplete
documentation. Swagger Core replaces it, and produces the OpenAPI specification
of the REST services out of both the JAX-RS and the OpenAPI annotations.
What doesn't depend on the project is managed here, so that any project
documenting its REST API out of a module of its own takes it from this POM:
* the plugin of Swagger, its output, the base document carrying the info
section that OpenAPI requires and that the plugin has no parameter to fill
in, and the binding of its resolve goal to the compile phase -- that goal
forks no compilation, so the site lifecycle alone would publish a page
without any specification;
* RESTEasy among the dependencies of the plugin: its scan by reflection loads
the classes of the project, some of them referring types that are otherwise
absent from the classpath of the plugin;
* the annotations of Swagger, and swagger-core for core-rs to compile the
filter completing the responses common to every endpoint and the resolver
making the schemas aware of the JAXB annotations; both are declared here as
well, core-rs providing them to every project;
* the version of Redoc, which renders the documentation;
* the execution dropping from the Maven site what isn't that documentation.
Only a module declaring the clean plugin inherits it.
The executions of the resources and of the dependency plugins are left to the
documentation modules, although they are the same in both projects: those two
plugins are declared here for every module of every project, which would unpack
Redoc into each of their sites.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-15 16:26:20 +0200c35c3985f86f4b10ff2dc6b681fce9d45575a3c8Manage the tooling generating the documentation of the REST APIeditpom.xml
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse300https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/300/Démarré à distance par l'hôte 140.82.115.34140.82.115.343005b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/master5b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/master5b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git300f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom300a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom3005a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/master5a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/master5a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2608213604739009Silverpeas_Project_Definition_AutoDeploy 2.0-build260821300false30058301SUCCESS1787326041455https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/300/false301https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/301/299https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/299/Démarré à distance par l'hôte 140.82.115.168140.82.115.1682995b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/master5b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/master5b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git299f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom299a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom2995a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/master5a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/master5a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2608214030439009Silverpeas_Project_Definition_AutoDeploy 2.0-build260821299false29958273SUCCESS1787325486434https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/299/false300https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/300/298https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/298/Démarré à distance par l'hôte 140.82.115.116140.82.115.116Started by GitHub push by mmoqui2985b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/master5b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/master5b79d885d26d617ef109b485fb9832a9185c5ce05b79d885d26d617ef109b485fb9832a9185c5ce0refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git298f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom298a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom2985a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/master5a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/master5a370360b2c7d47ec2960e23ab68acc658633a825a370360b2c7d47ec2960e23ab68acc658633a82refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2608203784039009Silverpeas_Project_Definition_AutoDeploy 2.0-build260820298false29858115SUCCESS1787231175897https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/298/false299https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/299/297https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/297/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-build2608203983839009Silverpeas_Project_Definition_AutoDeploy 2.0-build260820297false29758103SUCCESS1787231155896https://integration.silverpeas.org/jenkins/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.xml
git- pom.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.xml
- pom.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.xml
- pom.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.xml
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse298https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/298/blueDé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-build2608203983839009Silverpeas_Project_Definition_AutoDeploy 2.0-build260820297false29758103SUCCESS1787231155896https://integration.silverpeas.org/jenkins/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.xml
git- pom.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.xml
- pom.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.xml
- pom.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.xml
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse298https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/298/Stabilité du build : Aucun build récent n'a échoué.icon-health-80plushealth-80plus.png100falseDémarré à distance par l'hôte 140.82.115.31140.82.115.31Started by GitHub push by mmoqui301b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git301f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom301a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom301c35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2609154067639009Silverpeas_Project_Definition_AutoDeploy 2.0-build260915301false30159674SUCCESS1789482429565https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/301/- src/releases/silverpeas/Jenkinsfilesrc/builds/silverpeas/Jenkinsfile7e3556671c10e320bbd1de57e3638d1b427e63131788341397000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comFor the pipelines dedicated to build a build version of Silverpeas and
to release a stable version of Silverpeas (from a build version), mount
in the Docker container the file ~/.gradle/gradle.properties
configuration file in which should be defined the credentials for
publishing artefacts into our Maven/Gradle repo.
2026-09-02 11:29:57 +02007e3556671c10e320bbd1de57e3638d1b427e6313For the pipelines dedicated to build a build version of Silverpeas andeditsrc/releases/silverpeas/Jenkinsfileeditsrc/builds/silverpeas/Jenkinsfile
- src/releases/docker-build/Jenkinsfileb3a0a7bf423a3407c3bc6980f30a0c6ee678b5ae1788354644000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comNow by default Java version is 21 in the pipeline for building the project build Docker image
2026-09-02 15:10:44 +0200b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeNow by default Java version is 21 in the pipeline for building the project build Docker imageeditsrc/releases/docker-build/Jenkinsfile
git- pom.xmlc35c3985f86f4b10ff2dc6b681fce9d45575a3c81789482380000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comManage the tooling generating the documentation of the REST API
Smart-Doc is unable to document our REST API in a reliable way: it fails on
constructs we rely on, and reports a success while producing an incomplete
documentation. Swagger Core replaces it, and produces the OpenAPI specification
of the REST services out of both the JAX-RS and the OpenAPI annotations.
What doesn't depend on the project is managed here, so that any project
documenting its REST API out of a module of its own takes it from this POM:
* the plugin of Swagger, its output, the base document carrying the info
section that OpenAPI requires and that the plugin has no parameter to fill
in, and the binding of its resolve goal to the compile phase -- that goal
forks no compilation, so the site lifecycle alone would publish a page
without any specification;
* RESTEasy among the dependencies of the plugin: its scan by reflection loads
the classes of the project, some of them referring types that are otherwise
absent from the classpath of the plugin;
* the annotations of Swagger, and swagger-core for core-rs to compile the
filter completing the responses common to every endpoint and the resolver
making the schemas aware of the JAXB annotations; both are declared here as
well, core-rs providing them to every project;
* the version of Redoc, which renders the documentation;
* the execution dropping from the Maven site what isn't that documentation.
Only a module declaring the clean plugin inherits it.
The executions of the resources and of the dependency plugins are left to the
documentation modules, although they are the same in both projects: those two
plugins are declared here for every module of every project, which would unpack
Redoc into each of their sites.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-15 16:26:20 +0200c35c3985f86f4b10ff2dc6b681fce9d45575a3c8Manage the tooling generating the documentation of the REST APIeditpom.xml
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse300https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/300/Démarré à distance par l'hôte 140.82.115.31140.82.115.31Started by GitHub push by mmoqui301b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git301f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom301a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom301c35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2609154067639009Silverpeas_Project_Definition_AutoDeploy 2.0-build260915301false30159674SUCCESS1789482429565https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/301/- src/releases/silverpeas/Jenkinsfilesrc/builds/silverpeas/Jenkinsfile7e3556671c10e320bbd1de57e3638d1b427e63131788341397000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comFor the pipelines dedicated to build a build version of Silverpeas and
to release a stable version of Silverpeas (from a build version), mount
in the Docker container the file ~/.gradle/gradle.properties
configuration file in which should be defined the credentials for
publishing artefacts into our Maven/Gradle repo.
2026-09-02 11:29:57 +02007e3556671c10e320bbd1de57e3638d1b427e6313For the pipelines dedicated to build a build version of Silverpeas andeditsrc/releases/silverpeas/Jenkinsfileeditsrc/builds/silverpeas/Jenkinsfile
- src/releases/docker-build/Jenkinsfileb3a0a7bf423a3407c3bc6980f30a0c6ee678b5ae1788354644000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comNow by default Java version is 21 in the pipeline for building the project build Docker image
2026-09-02 15:10:44 +0200b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeNow by default Java version is 21 in the pipeline for building the project build Docker imageeditsrc/releases/docker-build/Jenkinsfile
git- pom.xmlc35c3985f86f4b10ff2dc6b681fce9d45575a3c81789482380000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comManage the tooling generating the documentation of the REST API
Smart-Doc is unable to document our REST API in a reliable way: it fails on
constructs we rely on, and reports a success while producing an incomplete
documentation. Swagger Core replaces it, and produces the OpenAPI specification
of the REST services out of both the JAX-RS and the OpenAPI annotations.
What doesn't depend on the project is managed here, so that any project
documenting its REST API out of a module of its own takes it from this POM:
* the plugin of Swagger, its output, the base document carrying the info
section that OpenAPI requires and that the plugin has no parameter to fill
in, and the binding of its resolve goal to the compile phase -- that goal
forks no compilation, so the site lifecycle alone would publish a page
without any specification;
* RESTEasy among the dependencies of the plugin: its scan by reflection loads
the classes of the project, some of them referring types that are otherwise
absent from the classpath of the plugin;
* the annotations of Swagger, and swagger-core for core-rs to compile the
filter completing the responses common to every endpoint and the resolver
making the schemas aware of the JAXB annotations; both are declared here as
well, core-rs providing them to every project;
* the version of Redoc, which renders the documentation;
* the execution dropping from the Maven site what isn't that documentation.
Only a module declaring the clean plugin inherits it.
The executions of the resources and of the dependency plugins are left to the
documentation modules, although they are the same in both projects: those two
plugins are declared here for every module of every project, which would unpack
Redoc into each of their sites.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-15 16:26:20 +0200c35c3985f86f4b10ff2dc6b681fce9d45575a3c8Manage the tooling generating the documentation of the REST APIeditpom.xml
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse300https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/300/Démarré à distance par l'hôte 140.82.115.31140.82.115.31Started by GitHub push by mmoqui301b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git301f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom301a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom301c35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2609154067639009Silverpeas_Project_Definition_AutoDeploy 2.0-build260915301false30159674SUCCESS1789482429565https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/301/- src/releases/silverpeas/Jenkinsfilesrc/builds/silverpeas/Jenkinsfile7e3556671c10e320bbd1de57e3638d1b427e63131788341397000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comFor the pipelines dedicated to build a build version of Silverpeas and
to release a stable version of Silverpeas (from a build version), mount
in the Docker container the file ~/.gradle/gradle.properties
configuration file in which should be defined the credentials for
publishing artefacts into our Maven/Gradle repo.
2026-09-02 11:29:57 +02007e3556671c10e320bbd1de57e3638d1b427e6313For the pipelines dedicated to build a build version of Silverpeas andeditsrc/releases/silverpeas/Jenkinsfileeditsrc/builds/silverpeas/Jenkinsfile
- src/releases/docker-build/Jenkinsfileb3a0a7bf423a3407c3bc6980f30a0c6ee678b5ae1788354644000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comNow by default Java version is 21 in the pipeline for building the project build Docker image
2026-09-02 15:10:44 +0200b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeNow by default Java version is 21 in the pipeline for building the project build Docker imageeditsrc/releases/docker-build/Jenkinsfile
git- pom.xmlc35c3985f86f4b10ff2dc6b681fce9d45575a3c81789482380000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comManage the tooling generating the documentation of the REST API
Smart-Doc is unable to document our REST API in a reliable way: it fails on
constructs we rely on, and reports a success while producing an incomplete
documentation. Swagger Core replaces it, and produces the OpenAPI specification
of the REST services out of both the JAX-RS and the OpenAPI annotations.
What doesn't depend on the project is managed here, so that any project
documenting its REST API out of a module of its own takes it from this POM:
* the plugin of Swagger, its output, the base document carrying the info
section that OpenAPI requires and that the plugin has no parameter to fill
in, and the binding of its resolve goal to the compile phase -- that goal
forks no compilation, so the site lifecycle alone would publish a page
without any specification;
* RESTEasy among the dependencies of the plugin: its scan by reflection loads
the classes of the project, some of them referring types that are otherwise
absent from the classpath of the plugin;
* the annotations of Swagger, and swagger-core for core-rs to compile the
filter completing the responses common to every endpoint and the resolver
making the schemas aware of the JAXB annotations; both are declared here as
well, core-rs providing them to every project;
* the version of Redoc, which renders the documentation;
* the execution dropping from the Maven site what isn't that documentation.
Only a module declaring the clean plugin inherits it.
The executions of the resources and of the dependency plugins are left to the
documentation modules, although they are the same in both projects: those two
plugins are declared here for every module of every project, which would unpack
Redoc into each of their sites.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-15 16:26:20 +0200c35c3985f86f4b10ff2dc6b681fce9d45575a3c8Manage the tooling generating the documentation of the REST APIeditpom.xml
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse300https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/300/Démarré à distance par l'hôte 140.82.115.31140.82.115.31Started by GitHub push by mmoqui301b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git301f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom301a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom301c35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2609154067639009Silverpeas_Project_Definition_AutoDeploy 2.0-build260915301false30159674SUCCESS1789482429565https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/301/- src/releases/silverpeas/Jenkinsfilesrc/builds/silverpeas/Jenkinsfile7e3556671c10e320bbd1de57e3638d1b427e63131788341397000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comFor the pipelines dedicated to build a build version of Silverpeas and
to release a stable version of Silverpeas (from a build version), mount
in the Docker container the file ~/.gradle/gradle.properties
configuration file in which should be defined the credentials for
publishing artefacts into our Maven/Gradle repo.
2026-09-02 11:29:57 +02007e3556671c10e320bbd1de57e3638d1b427e6313For the pipelines dedicated to build a build version of Silverpeas andeditsrc/releases/silverpeas/Jenkinsfileeditsrc/builds/silverpeas/Jenkinsfile
- src/releases/docker-build/Jenkinsfileb3a0a7bf423a3407c3bc6980f30a0c6ee678b5ae1788354644000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comNow by default Java version is 21 in the pipeline for building the project build Docker image
2026-09-02 15:10:44 +0200b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeNow by default Java version is 21 in the pipeline for building the project build Docker imageeditsrc/releases/docker-build/Jenkinsfile
git- pom.xmlc35c3985f86f4b10ff2dc6b681fce9d45575a3c81789482380000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comManage the tooling generating the documentation of the REST API
Smart-Doc is unable to document our REST API in a reliable way: it fails on
constructs we rely on, and reports a success while producing an incomplete
documentation. Swagger Core replaces it, and produces the OpenAPI specification
of the REST services out of both the JAX-RS and the OpenAPI annotations.
What doesn't depend on the project is managed here, so that any project
documenting its REST API out of a module of its own takes it from this POM:
* the plugin of Swagger, its output, the base document carrying the info
section that OpenAPI requires and that the plugin has no parameter to fill
in, and the binding of its resolve goal to the compile phase -- that goal
forks no compilation, so the site lifecycle alone would publish a page
without any specification;
* RESTEasy among the dependencies of the plugin: its scan by reflection loads
the classes of the project, some of them referring types that are otherwise
absent from the classpath of the plugin;
* the annotations of Swagger, and swagger-core for core-rs to compile the
filter completing the responses common to every endpoint and the resolver
making the schemas aware of the JAXB annotations; both are declared here as
well, core-rs providing them to every project;
* the version of Redoc, which renders the documentation;
* the execution dropping from the Maven site what isn't that documentation.
Only a module declaring the clean plugin inherits it.
The executions of the resources and of the dependency plugins are left to the
documentation modules, although they are the same in both projects: those two
plugins are declared here for every module of every project, which would unpack
Redoc into each of their sites.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-15 16:26:20 +0200c35c3985f86f4b10ff2dc6b681fce9d45575a3c8Manage the tooling generating the documentation of the REST APIeditpom.xml
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse300https://integration.silverpeas.org/jenkins/job/Silverpeas_Project_Definition_AutoDeploy/300/302truefalsefalsefalse