2 Replies Latest reply on Dec 27, 2012 5:43 AM by mikevan

    Missing file from Nexus preventing build of Arquillian TestNG Integration

    mikevan Newbie

      After downloading the most recent codebase from git for jbossAS 7.2.0.SNAPSHOT, I recieved the following error:

      [INFO] ------------------------------------------------------------------------

      [INFO] Building JBoss Application Server: Arquillian TestNG Integration 7.2.0.Alpha1-SNAPSHOT

      [INFO] ------------------------------------------------------------------------

      Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jboss-as-spec-api/7.2.0.Alpha1-SNAPSHOT/maven-metadata.xml

      Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jboss-as-spec-api/7.2.0.Alpha1-SNAPSHOT/jboss-as-spec-api-7.2.0.Alpha1-SNAPSHOT.pom

      [WARNING] The POM for org.jboss.as:jboss-as-spec-api:pom:7.2.0.Alpha1-SNAPSHOT is missing, no dependency information available

      [INFO] ------------------------------------------------------------------------

      [INFO] Reactor Summary:

      [INFO]

      [INFO] JBoss Application Server: Arquillian .............. SUCCESS [3.091s]

      [INFO] JBoss Application Server: Arquillian TestEnricher MSC  SUCCESS [7.331s]

      [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [7.461s]

      [INFO] JBoss Application Server: Arquillian Embedded Container  SUCCESS [18.654s]

      [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [3.766s]

      [INFO] JBoss Application Server: Arquillian Managed Container  SUCCESS [19.634s]

      [INFO] JBoss Application Server: Arquillian Remote Container  SUCCESS [2.147s]

      [INFO] JBoss Application Server: Arquillian TestNG Integration  FAILURE [3.535s]

      [INFO] JBoss Application Server: Arquillian Common Domain  SKIPPED

      [INFO] JBoss Application Server: Arquillian Remote Domain Container  SKIPPED

      [INFO] JBoss Application Server: Arquillian Managed Domain Container  SKIPPED

      [INFO] ------------------------------------------------------------------------

      [INFO] BUILD FAILURE

      [INFO] ------------------------------------------------------------------------

      [INFO] Total time: 1:08.150s

      [INFO] Finished at: Sat Dec 22 23:43:21 PST 2012

      [INFO] Final Memory: 51M/317M

      [INFO] ------------------------------------------------------------------------

      [ERROR] Failed to execute goal on project jboss-as-arquillian-testng-integration: Could not resolve dependencies for project org.jboss.as:jboss-as-arquillian-testng-integration:jar:7.2.0.Alpha1-SNAPSHOT

       

      Indeed after looking at the jboss nexus repository I came across this link:

      https://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jboss-as-spec-api/

       

      There do not appear to be any entries for 7.2.0.Alpha1-SNAPSHOT. Any ideas what's going on?

        • 1. Re: Missing file from Nexus preventing build of Arquillian TestNG Integration
          mikevan Newbie

          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.

           

          Thoughts?

           

          -- Mike Van

          Apache Software Foundation, Committer

          1 of 1 people found this helpful
          • 2. Re: Missing file from Nexus preventing build of Arquillian TestNG Integration
            mikevan Newbie

            Option two of this thread has been implemented and a patch named "0001-Moved-testng-integration-to-the-base-directory-and-m.patch " has now been attached to https://issues.jboss.org/browse/AS7-6248 .  This patch has been released under ASF 2.0 license.

             

            -- Mike Van

            Apache Software Foundation, Committer