Branch: refs/heads/misc-flavor-security-docker-test Home: https://github.com/xwiki/xwiki-platform Commit: ef149f412c978299879f685f341f375fa68549ae https://github.com/xwiki/xwiki-platform/commit/ef149f412c978299879f685f341f3... Author: Vincent Massol <[email protected]> Date: 2026-07-24 (Fri, 24 Jul 2026) Changed paths: M xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test/pom.xml M xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test/xwiki-platform-distribution-flavor-test-security/pom.xml A xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test/xwiki-platform-distribution-flavor-test-security/src/test/it/org/xwiki/test/security/AllIT.java R xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test/xwiki-platform-distribution-flavor-test-security/src/test/it/org/xwiki/test/security/AllTests.java R xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test/xwiki-platform-distribution-flavor-test-security/src/test/it/org/xwiki/test/security/ExtensionSecurityTest.java A xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test/xwiki-platform-distribution-flavor-test-security/src/test/it/org/xwiki/test/security/FlavorExtensionSecurityScanIT.java Log Message: ----------- [Misc] Convert the flavor extension-security functional test to the Docker framework Convert ExtensionSecurityTest from the JUnit4 legacy framework (AbstractTest + a PageObjectSuite runner starting XWiki out of process) to the JUnit5 Docker framework, in place: the test keeps its own xwiki-platform-distribution-flavor-test-security module and its own 'Flavor Test - Security' CI job. The test keeps its scenario and its assertion unchanged: index the installed extensions, open the Extension Vulnerabilities admin section, and require that no CVE is left to review. It runs on @UITest(standardFlavor = true), so the scan still covers the extensions of a standard flavor instance. Module changes: - Packaging pom -> jar, with src/test/it as test sources and failsafe, which runs AllIT. The legacy compiler/resources/dependency/surefire configuration goes away, and so does the AllTests runner: the framework now configures the maven-local extension repository and the test logs in itself. - The extension security UI is not bundled by the standard flavor nor by the WAR core extensions, so it still has to be provisioned. Instead of installing it from the test body over REST, it is declared as a runtime-scoped xar dependency, which the framework installs at startup. The REST installer dependencies (xwiki-platform-test-rest, jakarta.servlet-api) are dropped. - banneddependencytype-xar is skipped: that rule keeps JAR extensions from pulling XAR extensions at runtime, and it exempts modules named *-test-docker only. This module is a functional test module, never installed as an extension, and it needs the XAR to provision the feature under test. - The module moves to the docker profile of the flavor test parent pom, as is done for every other Docker test module, so that a build without a Docker daemon does not pick it up. The CI job is unaffected since it builds the module pom directly. The test class is named FlavorExtensionSecurityScanIT to keep it distinct from ExtensionSecurityIT in xwiki-platform-extension-security-test-docker, which covers the same feature against mocked vulnerability sources. To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-platform/settings/notifications