[jboss-jira] [JBoss JIRA] (AS7-6248) Missing file from Nexus preventing build of Arquillian TestNG Integration

[ https://issues.jboss.org/browse/AS7-6248?page=com.atlassian.jira.plugin.s... ] Michael Van Geertruy edited comment on AS7-6248 at 12/23/12 4:44 AM: --------------------------------------------------------------------- This file is created by the spec-api module, which is built much later in the build process. The way I see it, there are two possible solutions: 1) Move the arquillian modules to after the spec-api module (destructive), or 2) Create a module specifically for arquillian-testng at a peer level to spec-api in the source-tree and move the contents of arquillian-testng to the new module. In the project's parent pom.xml, create an entry for arquillian-testng immediately after spec-api in the modules section. 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. I can implement whichever solution you folks would like and submit a patch after a decision is made. The only reason I found this was because I started the build with 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. was (Author: mikevan): This file is created by the spec-api module, which is built much later in the build process. The way I see it, there are two possible solutions: 1) Move the arquillian modules to after the spec-api module. 2) Create a module specifically for arquillian-testng at a peer level to spec-api in the source-tree and move the contents of arquillian-testng to the new module. In the project's parent pom.xml, create an entry for arquillian-testng immediately after spec-api in the modules section. 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. I can implement whichever solution you folks would like and submit a patch after a decision is made. The only reason I found this was because I started the build with 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira