1 Reply Latest reply on Oct 18, 2011 7:09 AM by Aslak Knutsen

    Arquillian w/o Maven/Gradle/Ivy on JBoss AS7?

    garvin dean Newbie

      First, I love what I've read about Arquillian- and, I've read a lot as in pretty much all of the forum posts on it and the guides. However, my situation is that we are not able to leverage maven in our build environment- we're stuck on ANT- at some point we may bring in Ivy. I've a "few" questions:

       

      1) can Arquillian run in a maven/gradle/ivy free environment- just plain ole "ant"?

      2) is it possible to use maven only for Arquillian dependencies and not mavenize the underlying project?

      3) are there any "simple" practical examples?

       

       

      I "think" I've made my way through the dependency chain- but, what I can't figure out is how to handle the maven profile that seems to be integral to this thing working!! could be wrong...

       

      If anyone can show a functional configuration to test with @EJB in a test case, to include arquillian.xml and classpath setup without using maven or gradle, I'd really appreciate it!!

        • 1. Re: Arquillian w/o Maven/Gradle/Ivy on JBoss AS7?
          Aslak Knutsen Master

          I can show you one without Maven and Gradle but using Ivy.

           

          https://github.com/arquillian/arquillian-showcase/blob/master/cdi/build.xml

           

          A pure ANT example would be very similar, you just have to handle the dependencies your self.

           

          To answer your questions:

           

          1) Yes, but you need to manually configure the dependencies. The best way to see which are required is by using a Ivy/Gradle/Maven and have it print out it's dependencies.

           

          2) I guess you could create a Maven pom that defines the dependencies and output them to a folder on disk. You can then call this from ANT and include the output folder on your classpath. Using ivy is probably a better solution tho.

           

          3) see above..

           

           

          Maven Profiles are only used to 'isolate' the classpath when you need to run with multiple containers, e.g. JBoss AS 6 and 7 or Remote and Managed containers. Arquillian only allow one type of container on classpath at runtime.

          1 of 1 people found this helpful