Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Pulsar
Description
When running the l10n maven plugin report phase using multiple thread the build fails on a regular basis:
[ERROR] Failed to execute goal org.onehippo.cms.l10n:hippo-cms-l10n-maven-plugin:14.2.1:report (report) on project hippo-essentials-components-l10n: Execution report of goal org.onehippo.cms.l10n:hippo-cms-l10n-maven-plugin:14.2.1:report failed. FileSystemAlreadyExistsException org.apache.maven.lifecycle.LifecycleExecutionException: Caused by: java.nio.file.FileSystemAlreadyExistsException at com.sun.nio.zipfs.ZipFileSystemProvider.newFileSystem (ZipFileSystemProvider.java:113) at java.nio.file.FileSystems.newFileSystem (FileSystems.java:326) at java.nio.file.FileSystems.newFileSystem (FileSystems.java:276) at org.onehippo.cms.l10n.RepositoryResourceBundleLoader.createZipFileSystem (RepositoryResourceBundleLoader.java:86) at org.onehippo.cms.l10n.RepositoryResourceBundleLoader.collectResourceBundles (RepositoryResourceBundleLoader.java:60) at org.onehippo.cms.l10n.ResourceBundleLoader.loadBundles (ResourceBundleLoader.java:40) at org.onehippo.cms.l10n.Registrar.scan (Registrar.java:153) at org.onehippo.cms.l10n.Registrar.report (Registrar.java:145) at org.onehippo.cms.l10n.ReportMojo.execute (ReportMojo.java:47)
To reproduce run the translations module with mvn clean verify -DskipTests -T1C
Note the report scans all modules on the classpath matching specific GroupIds, see org/onehippo/cms/l10n/ArtifactInfo.java:88
Common modules such as hippo-repository-api and hippo-cms7-commons are scanned for each submodule. As FileSystems return static file systems and those can be closed ResourceBundleLoader might fail
Attachments
Issue Links
- is duplicated by
-
CMS-12442 l10n plugin is not threadsafe and builds occasionally fail if Maven threading is used
- Closed