api-regions-exportsimports leads to failure in Cloud Manager build but not in aemanalyser-maven-plugin

[kwin]

The Cloud Manager build fails (correctly) with

2024-04-08 10:21:55.796 Convert Merge Analyse version [0.5.180]
2024-04-08 10:22:40.977 Analyser warnings have been found 
2024-04-08 10:22:40.977 The analyser found the following warnings for author and publish : 
...
2024-04-08 10:22:40.978 The analyser found the following errors for author and publish : 
2024-04-08 10:22:40.978 [api-regions-exportsimports] <myBundle> is importing package(s) [org.dom4j.tree, org.jdom.input, org.jdom, org.dom4j.io, org.dom4j] in start level 20 but no bundle is exporting these for that start level. (<group>:<name>:<version>)

But the local build including aemanalyser-maven-plugin 1.5.8 with goal project-analyze does (incorrectly) not fail

[DEBUG] Configuring mojo execution 'com.adobe.aem:aemanalyser-maven-plugin:1.5.8:project-analyse:analyser' with basic configurator -->
[DEBUG]   (f) analyserTasks = [requirements-capabilities, api-regions, api-regions-check-order, api-regions-crossfeature-dups, api-regions-exportsimports, region-deprecated-api]
[DEBUG]   (f) analyserUserTasks = [bundle-resources, bundle-nativecode, bundle-unversioned-packages, artifact-rules, configuration-api, aem-env-var, repoinit, content-packages-validation]
[DEBUG]   (f) failOnAnalyserErrors = true
[DEBUG]   (f) mavenSession = org.apache.maven.execution.MavenSession@527a8665
[DEBUG]   (f) plugin = Component Descriptor: role: 'org.apache.maven.plugin.Mojo', implementation: 'com.adobe.aem.analyser.mojos.DeprecatedAggregateMojo', role hint: 'com.adobe.aem:aemanalyser-maven-plugin:1.5.8:aggregate'
role: 'org.apache.maven.plugin.Mojo', implementation: 'com.adobe.aem.analyser.mojos.AnalyseMojo', role hint: 'com.adobe.aem:aemanalyser-maven-plugin:1.5.8:analyse'
role: 'org.apache.maven.plugin.Mojo', implementation: 'com.adobe.aem.analyser.mojos.AnalyseConfigsMojo', role hint: 'com.adobe.aem:aemanalyser-maven-plugin:1.5.8:analyse-configs'
role: 'org.apache.maven.plugin.Mojo', implementation: 'com.adobe.aem.analyser.mojos.DeprecatedConvertMojo', role hint: 'com.adobe.aem:aemanalyser-maven-plugin:1.5.8:convert'
role: 'org.apache.maven.plugin.Mojo', implementation: 'com.adobe.aem.analyser.mojos.HelpMojo', role hint: 'com.adobe.aem:aemanalyser-maven-plugin:1.5.8:help'
role: 'org.apache.maven.plugin.Mojo', implementation: 'com.adobe.aem.analyser.mojos.PackageAppMojo', role hint: 'com.adobe.aem:aemanalyser-maven-plugin:1.5.8:package-app'
role: 'org.apache.maven.plugin.Mojo', implementation: 'com.adobe.aem.analyser.mojos.ProjectAnalyseMojo', role hint: 'com.adobe.aem:aemanalyser-maven-plugin:1.5.8:project-analyse'
---
[DEBUG]   (f) project = MavenProject: ...all-container/pom.xml
[DEBUG]   (f) repoSession = org.eclipse.aether.DefaultRepositorySystemSession@a323a5b
[DEBUG]   (f) skip = false
[DEBUG]   (f) skipAnalyserTasks = []
[DEBUG]   (f) skipAnalyserUserTasks = []
[DEBUG]   (f) strictValidation = false
[DEBUG]   (f) useDependencyVersions = false
[DEBUG]   (f) useSysout = false
[DEBUG] -- end configuration --
... 
[INFO] - Executing Bundle Import/Export Check [api-regions-exportsimports]...
[INFO] - Executed Bundle Import/Export Check [api-regions-exportsimports] in 870ms

for either of the aggregated builds. So there seems to be something configured differently between those two tools.