Hi, Windows as you might know has some problems with long file paths..
https://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath And Maven is.. well, very fond of long paths. :) This can causes issues such as with surefire forked execution and the Archetype integration test which does an inner maven execution, e.g. [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project dummy-taverna-plugin-activity: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:t est failed: The forked VM terminated without properly saying goodbye. VM crash or System.exit called? [INFO] [ERROR] Command was cmd.exe /X /C ""C:\Program Files\Java\jdk1.8.0_51\jre\bin\java" -jar C:\Users\alson\taverna\apache-taverna-engine-3.1.0-incubating-source-release\apache-taverna-engine-3.1.0-incubating\taverna-activity-archetype\target\test-classes\projects\dummyActivity\project\dummy-taverna-plugin\dummy-taverna-plugin-activity\target\surefire\surefirebooter1896791380795738239.jar Often moving the checked out source code to say C:\src\ fixes the problem. Rather than simply disabling all tests on Windows, is there a way we can detect this situation in advance from a master pom-file? E.g. some kind of "This project need at least 140 path characters free on Windows" check - ideally with a suggestion on unpacking the project at a shorter folder. Or some kind of <activation> so we can disable those forking tests if the folder is incompatible? -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons http://orcid.org/0000-0001-9842-9718
