This file is created by the spec-api module, which is created much later in the build process. The way I see it, there are two possible solutions:
- Move the arquillian modules to after the spec-api module.
- Create a module specifically for arquillian-testng and execute that module immediately after spec-api is built.
The only other module that has a dependency on jboss-as-arquillian-testng-integration is test-suite which runs after spec-api. Also, all of the other Arquillian modules build fine, and there are numerous dependencies on the other arquillian modules in the build process. With this in mind, I think option 2 is probably best.
Either way, I think this deserves a Jira. I can implement whichever solution you folks would like and submit a patch to the ticket tomorrow.
The only reason I found this was because I started the build with a from a blank .m2/repository. If Jenkins isn't clearing out the .m2/repository prior to the build that then this would have only shown up the first time a build was done. After that, the file produced by spec-api would be installed into the repository and the problem would have gone away.
Thoughts?
-- Mike Van
Apache Software Foundation, Committer