Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-1455

BOMs for JBAS 7.1.1.Final seem to have the wrong dependencies to ARQ

XMLWordPrintable

    • Hide

      See the attached zip file which is basically the outcome of the ARQ tutorial in http://arquillian.org/guides/getting_started/

      D/L and unpack JBoss AS 7.1.1.Final into the project.base.directory (parallel to src, or somewhere else, see path in src/test/resources/arquillian.xml)

      Build with
      mvn -f pom.tutorial-working.xml clean test
      => works OK, as expected

      Build with
      mvn clean test -Parquillian-jbossas-managed-713
      => Version hiccup, test fails for some obscure reason

      Build with
      mvn clean test -Parquillian-jbossas-managed-711
      => Works (manually overriding the settings from the BOM)

      Show
      See the attached zip file which is basically the outcome of the ARQ tutorial in http://arquillian.org/guides/getting_started/ D/L and unpack JBoss AS 7.1.1.Final into the project.base.directory (parallel to src, or somewhere else, see path in src/test/resources/arquillian.xml) Build with mvn -f pom.tutorial-working.xml clean test => works OK, as expected Build with mvn clean test -Parquillian-jbossas-managed-713 => Version hiccup, test fails for some obscure reason Build with mvn clean test -Parquillian-jbossas-managed-711 => Works (manually overriding the settings from the BOM)

      When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM.

      I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with

      • org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container
      • Managed server was not started within [60] s

      Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on.

      After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now.

      This bug report is mainly to help people that run into the same problem.

      Kind regards,
      and cheers for an awesome product
      David

              Unassigned Unassigned
              dxmann73@gmail.com David Mann (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: