[
https://issues.apache.org/jira/browse/SLING-7318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296753#comment-16296753
]
Konrad Windszus commented on SLING-7318:
----------------------------------------
Indeed the pom.xml now depends on a different version of commons.osgi (2.4.0,
has actually been broken two years ago via
https://github.com/apache/sling-slingstart-maven-plugin/commit/03c236beb2ab47c7a11e1e3cb75f9589dddf39f2)
and the test in PreparePackageMojoTest
(https://github.com/apache/sling-slingstart-maven-plugin/blob/bec3fb21360e34c49329ad54f43336f47f79df36/src/test/java/org/apache/sling/maven/slingstart/PreparePackageMojoTest.java#L147)
has not been adjusted after this commit. We should find a more reliable way to
make sure that pom and test use the same versions.
> PreparePackageMojoTest.testSubsystemBaseGeneration fails intermittently
> -----------------------------------------------------------------------
>
> Key: SLING-7318
> URL: https://issues.apache.org/jira/browse/SLING-7318
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
> Affects Versions: Slingstart Maven Plugin 1.7.10
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Minor
>
> In case the test execution fails the Maven output looks like this
> {code}
> org.apache.sling.maven.slingstart.PreparePackageMojoTest
> testSubsystemBaseGeneration(org.apache.sling.maven.slingstart.PreparePackageMojoTest)
> Time elapsed: 0.013 sec <<< ERROR!
> org.apache.maven.plugin.MojoExecutionException: Problem creating subsystem
> .esa file
> /tmp/PreparePackageMojoTest3862315247356430887/slingstart-tmp/test1.subsystem-base
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at
> sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
> at java.nio.file.Files.newByteChannel(Files.java:361)
> at java.nio.file.Files.newByteChannel(Files.java:407)
> at
> java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
> at java.nio.file.Files.newInputStream(Files.java:152)
> at java.nio.file.Files.copy(Files.java:3068)
> at
> org.apache.sling.maven.slingstart.PreparePackageMojo.createSubsystemBaseFile(PreparePackageMojo.java:382)
> at
> org.apache.sling.maven.slingstart.PreparePackageMojo.buildSubsystemBase(PreparePackageMojo.java:255)
> at
> org.apache.sling.maven.slingstart.PreparePackageMojo.buildContentsMap(PreparePackageMojo.java:235)
> at
> org.apache.sling.maven.slingstart.PreparePackageMojo.prepareGlobal(PreparePackageMojo.java:141)
> at
> org.apache.sling.maven.slingstart.PreparePackageMojo.execute(PreparePackageMojo.java:131)
> at
> org.apache.sling.maven.slingstart.PreparePackageMojoTest.testSubsystemBaseGeneration(PreparePackageMojoTest.java:176)
> {code}
> This happens from time to time also on the ASF Jenkins (e.g. in
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-slingstart-maven-plugin-1.8/12/org.apache.sling$slingstart-maven-plugin/console).
> This was also reported via
> https://www.mail-archive.com/[email protected]/msg73131.html.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
