experiment: isolate whether Dokka 2.2.0 breaks the CodeQL Kotlin extractor

pom.xml

@@ -25,6 +25,10 @@
         <jacoco.version>0.8.12</jacoco.version>
         <jspecify.version>1.0.1</jspecify.version>
         <spotless.version>2.43.0</spotless.version>
+        <!-- Dokka is this project's javadoc, so the standard switch skips it too: a build that asked for
+             no documentation should not load a documentation engine, let alone a second Kotlin generation
+             into the same JVM as the compiler. -->
+        <maven.javadoc.skip>false</maven.javadoc.skip>
     </properties>
     <groupId>st.orm</groupId>
     <artifactId>storm-framework</artifactId>

storm-kotlin-spring/pom.xml

@@ -74,6 +74,10 @@
                 <groupId>org.jetbrains.kotlin</groupId>
                 <artifactId>kotlin-maven-plugin</artifactId>
                 <version>${kotlin.version}</version>
+                <!-- Contributes the plugin's lifecycle mapping, which also synthesises default-compile and
+                     default-kapt executions beside the ones declared below. That duplication is deliberate for
+                     now: dropping it changed what CodeQL's Kotlin extractor sees and broke its analysis. -->
+                <extensions>true</extensions>
                 <configuration>
                     <jvmTarget>21</jvmTarget>
                     <args>

storm-ktor-test/pom.xml

@@ -56,6 +56,10 @@
                 <groupId>org.jetbrains.kotlin</groupId>
                 <artifactId>kotlin-maven-plugin</artifactId>
                 <version>${kotlin.version}</version>
+                <!-- Contributes the plugin's lifecycle mapping, which also synthesises default-compile and
+                     default-kapt executions beside the ones declared below. That duplication is deliberate for
+                     now: dropping it changed what CodeQL's Kotlin extractor sees and broke its analysis. -->
+                <extensions>true</extensions>
                 <configuration>
                     <jvmTarget>21</jvmTarget>
                     <args>
@@ -141,14 +145,12 @@
             <plugin>
                 <groupId>org.jetbrains.dokka</groupId>
                 <artifactId>dokka-maven-plugin</artifactId>
-                <!-- Dokka 2.0 analyses with a Kotlin 2.0 frontend, which cannot read the Kotlin 2.3 metadata this
-                     module and its stdlib carry; 2.2 can. The rest of the framework stays on 2.0 with its own
-                     compiler generation. -->
                 <version>2.2.0</version>
                 <!-- The module has no Java sources, and Dokka's default source roots are the project's compile
                      roots, which include Maven's src/main/java whether it exists or not. Naming the Kotlin root
                      keeps a missing directory from being reported as an error on every build. -->
                 <configuration>
+                    <skip>${maven.javadoc.skip}</skip>
                     <sourceDirectories>
                         <dir>${project.basedir}/src/main/kotlin</dir>
                     </sourceDirectories>

storm-ktor/pom.xml

@@ -58,6 +58,10 @@
                 <groupId>org.jetbrains.kotlin</groupId>
                 <artifactId>kotlin-maven-plugin</artifactId>
                 <version>${kotlin.version}</version>
+                <!-- Contributes the plugin's lifecycle mapping, which also synthesises default-compile and
+                     default-kapt executions beside the ones declared below. That duplication is deliberate for
+                     now: dropping it changed what CodeQL's Kotlin extractor sees and broke its analysis. -->
+                <extensions>true</extensions>
                 <configuration>
                     <jvmTarget>21</jvmTarget>
                     <args>
@@ -169,14 +173,12 @@
             <plugin>
                 <groupId>org.jetbrains.dokka</groupId>
                 <artifactId>dokka-maven-plugin</artifactId>
-                <!-- Dokka 2.0 analyses with a Kotlin 2.0 frontend, which cannot read the Kotlin 2.3 metadata this
-                     module and its stdlib carry; 2.2 can. The rest of the framework stays on 2.0 with its own
-                     compiler generation. -->
                 <version>2.2.0</version>
                 <!-- The module has no Java sources, and Dokka's default source roots are the project's compile
                      roots, which include Maven's src/main/java whether it exists or not. Naming the Kotlin root
                      keeps a missing directory from being reported as an error on every build. -->
                 <configuration>
+                    <skip>${maven.javadoc.skip}</skip>
                     <sourceDirectories>
                         <dir>${project.basedir}/src/main/kotlin</dir>
                     </sourceDirectories>