I know the issue, but it is up to INFRA @ ASF to solve this.
It has worked in the past[1]
[1]
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-archetype/job/master/6/
On Thu, 16 Aug 2018 21:42:16 +0200, Stefan Seifert
<sseif...@pro-vision.de> wrote:
Cheered a bit too early.
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-
archetype/job/ARCHETYPE-553/
needs to be green first. After that it can be merged and can have a look
at your patch.
there seems to be a problem with the file system on the windows machines
- example stacktrace:
---
org.codehaus.plexus.util.cli.CommandLineException: Error while executing
process.
at
org.apache.maven.archetype.creator.DefaultArchetypeCreatorIT.createFilesetArchetype(DefaultArchetypeCreatorIT.java:136)
at
org.apache.maven.archetype.creator.DefaultArchetypeCreatorIT.testIncludeFileWithNoExtension(DefaultArchetypeCreatorIT.java:189)
Caused by: java.io.IOException: Cannot run program
"F:\jenkins\tools\maven\apache-maven-3.5.2\bin\mvn.cmd" (in directory
"F:\jenkins\jenkins-slave\workspace\ven-archetype_ARCHETYPE-553-J4FOCNZGBVSFDFI4P3DBC7GXGJK62NFN5QH7Q5I46GZ5AP3FIVLQ\windows-jdk9-m3.5.x_build\archetype-testing\archetype-final\target\test-classes\projects\include-file-with-no-extension\target\generated-sources\archetype"):
CreateProcess error=267, The directory name is invalid
at
org.apache.maven.archetype.creator.DefaultArchetypeCreatorIT.createFilesetArchetype(DefaultArchetypeCreatorIT.java:136)
at
org.apache.maven.archetype.creator.DefaultArchetypeCreatorIT.testIncludeFileWithNoExtension(DefaultArchetypeCreatorIT.java:189)
Caused by: java.io.IOException: CreateProcess error=267, The directory
name is invalid
at
org.apache.maven.archetype.creator.DefaultArchetypeCreatorIT.createFilesetArchetype(DefaultArchetypeCreatorIT.java:136)
at
org.apache.maven.archetype.creator.DefaultArchetypeCreatorIT.testIncludeFileWithNoExtension(DefaultArchetypeCreatorIT.java:189)
---
the build for this IT results in a file system path
---
F:\jenkins\jenkins-slave\workspace\ven-archetype_ARCHETYPE-553-J4FOCNZGBVSFDFI4P3DBC7GXGJK62NFN5QH7Q5I46GZ5AP3FIVLQ\windows-jdk9-m3.5.x_build\archetype-testing\archetype-final\target\test-classes\projects\include-file-with-no-extension\target\generated-sources\archetype
---
which is 260 chars long - longer than the usual limit of 255 chars on
windows file systems.
other integration tests that have shorter test names than
"include-file-with-no-extension" pass.
possible solutions:
1. (dirty hack) shorten all test names in [1] so that they have max. 30
chars or less.
2. shorten the root path that seems to be generated by jenkins for each
build
3. try to reconfigure the windows file systems on the jenkins slave to
allow more than 255 chars (may or may not work properly)
stefan
[1]
https://github.com/apache/maven-archetype/blob/master/archetype-testing/archetype-final/src/test/java/org/apache/maven/archetype/creator/DefaultArchetypeCreatorIT.java
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
