Arquillian Blog

The Arquillian team is proud to announce the 1.0.0.Alpha2 release of the Arquillian Maven Plugin component!

What is Arquillian?

Arquillian is open source software that empowers you to test JVM-based applications more effectively. Created to defend the software galaxy from bugs, Arquillian brings your test to the runtime so you can focus on testing your application's behavior rather than managing the runtime. Using Arquillian, you can develop a comprehensive suite of tests from the convenience of your IDE and run them in any IDE, build tool or continuous integration environment.

Release details

Component	Arquillian Maven Plugin
Version	1.0.0.Alpha2 view tag
Release date	2012-03-14
Released by	Aslak Knutsen
Compiled against	Arquillian Core – 1.0.0.CR7

Release notes and resolved issues 3

Support for Maven lifecycle binding

Feature Request

• ARQ-502 - Support arquillian.xml configuration in Maven Plugin
• ARQ-708 - Should support keeping container alive between execution phases

Thanks to the following list of contributors: Aslak Knutsen, Davide D'alto

Since we wrote this post we didn't laze around. Check our latest announcement.

The Arquillian team is proud to announce the 1.0.0.Alpha1 release of the Arquillian Maven Plugin component!

What is Arquillian?

Arquillian is open source software that empowers you to test JVM-based applications more effectively. Created to defend the software galaxy from bugs, Arquillian brings your test to the runtime so you can focus on testing your application's behavior rather than managing the runtime. Using Arquillian, you can develop a comprehensive suite of tests from the convenience of your IDE and run them in any IDE, build tool or continuous integration environment.

Release details

Component	Arquillian Maven Plugin
Version	1.0.0.Alpha1 view tag
Release date	2011-08-14
Released by	Aslak Knutsen
Compiled against	Arquillian Core – 1.0.0.CR1

Release notes and resolved issues 2

Extension Maven Plugin - Alpha1

Feature Request

• ARQ-501 - Support for 'profiles' inside the Maven Plugin configuration

Thanks to the following list of contributors: Aslak Knutsen

Great news! We’ve drastically cut down the number of dependencies that Maven has to download in order to use the JBoss AS 6 remote container adapter Arquillian. You no longer have to download Hibernate just to connect to a remote or managed (standalone) JBoss AS instance ~:)

To cut to the chase, replace this dependency:

<dependency>
   <groupId>org.jboss.jbossas</groupId>
   <artifactId>jboss-as-client</artifactId>
   <version>6.0.0.Final</version>
   <type>pom</type>
</dependency>

with this one:

<dependency>
  <groupId>org.jboss.jbossas</groupId>
  <artifactId>jboss-as-profileservice-client</artifactId>
  <version>6.0.0.Final</version>
  <type>pom</type>
</dependency>

The number of dependencies drops from 318 to just 28! That should save you a heaps of time. Now, Maven doesn’t have download these extra dependenices on the first run, and doesn’t have to resolve the graph on subsequent invocations. You also cut out this unresolved pom warning:

[WARNING] The POM for ws-commons:policy:jar:1.0 is invalid, transitive dependencies
(if any) will not be available, enable debug logging for more details

To make a long story short, the JBoss AS team publishes a stack POM (i.e., BOM) to identify all the dependencies used in JBoss AS. The client POM is a little too well linked and ends up depending on JBoss AS itself somewhere down the line. As you can imagine, this pulls in a lot of transitive dependencies.

The profile service client POM is a trimmed down version that grabs only the libraries needed for communicating with a remote (standalone) JBoss AS instance using the DeploymentManager, which is accessed via the ProfileService.

Cut the internet a break and update your POM today ~:)