Arquillian Blog

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

The Arquillian team is proud to announce the 2.2.0 release of the ShrinkWrap Resolver component!

The most significant change since the previous release is the postponing of the settings.xml loading.
Previously, when a user wanted to specify completely different settings.xml:

Maven.configureResolver().fromFile("path/to/my_settings.xml");

During the call configureResolver() the default settings.xml was immediately loaded and later on regenerated with the given my_settings.xml. This process could in some cases cause unexpected behavior (eg. the default settings.xml was corrupted).

In this new release, the loading has been postponed to the time when:

1. the settings.xml is needed (eg. artifacts resolving)
   or
2. the resolver is configured with some specific settings.xml (eg. calling fromFile("path/to/my_settings.xml"))

So, there is no change for the user in the usage – it now just does what the user wants (ie. when some different settings.xml is specified, the default one is never loaded).

Significant additions since the last final release 2.1.1:

Gradle importer
List resolution
MavenCoordinates as output
Better cooperation of MavenImporter and IDEs
Upgrade to Aether 1.0.0.v20140518
Upgrade to Maven 3.2.5

And many other bugfixes and feature requests. For more information see the release notes of the preceding alpha releases.

Big kudos to all contributors who helped to make this stable release.

We hope that you’ll enjoy our new release and look forward to hear your feedback on the community forums.

What is ShrinkWrap Resolver?

The ShrinkWrap Resolvers project provides a Java API to obtain artifacts from a repository system. This is handy to include third party libraries available in any Maven repository in your test archive. ShrinkWrap Resolvers additionally allow you to reuse all the configuration you've already specified in the Maven build file, making packaging of an application archive much easier job.

Release details

Component	ShrinkWrap Resolver
Version	2.2.0 view tag
Release date	2015-09-16
Released by	Matous Jobanek
Compiled against	JUnit – 4.11

Published artifacts org.jboss.shrinkwrap.resolver

• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-bom pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-gradle-embedded-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-depchain pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-gradle-depchain pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-gradle-embedded-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-api-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi-maven jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-impl-maven-archive jar javadoc pom
• org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-spi jar javadoc pom

Release notes and resolved issues 4

Feature Request

• SHRINKRES-226 - Loading of the settings.xml configuration should be postponed

Bug

• SHRINKRES-224 - Generated artifacts from workspace are missing directory entries
• SHRINKRES-229 - Fix the javadoc to meet JDK 8 requirements
• SHRINKRES-230 - Tests in ClasspathWorkspaceReaderTestCase are failing when running in IDE

Thanks to the following list of contributors: Matous Jobanek, Olivier Spieser, Michal Matloka, Karel Piwko

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.Alpha5 release of the Arquillian Container Chameleon component!

What is Arquillian Container Chameleon?

The Chameleon container can quickly adapt to your needs of testing against several containers (JBoss AS / JBoss EAP / WildFly / GlassFish) or even switching between different modes (Managed / Remote / Embedded) without requiring additional dependency configuration.

Release details

Component	Arquillian Container Chameleon
Version	1.0.0.Alpha5 view tag
Release date	2015-09-16
Released by	Aslak Knutsen
Compiled against	Arquillian Core – 1.1.8.Final

Published artifacts org.arquillian.container

• org.arquillian.container » arquillian-container-chameleon jar javadoc pom

Release notes and resolved issues 2

Enhancement

• #26 Add support for WildFly 10.x
• #25 Expose ability to load classes from Target Container ClassLoader

Thanks to the following list of contributors: Aslak Knutsen

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.Alpha5 release of the Arquillian Container SE 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 Container SE
Version	1.0.0.Alpha5 view tag
Release date	2015-09-11
Released by	Tomas Remes
Compiled against	Arquillian Core – 1.1.7.Final

Published artifacts org.jboss.arquillian.container

• org.jboss.arquillian.container » container-se-api jar javadoc pom
• org.jboss.arquillian.container » container-se-managed jar javadoc pom
• org.jboss.arquillian.container » container-se-server jar javadoc pom
• org.jboss.arquillian.container » container-se-tests jar javadoc pom

Thanks to the following list of contributors: Tomas Remes, Martin Kouba

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

The Arquillian team is proud to announce the 1.1.9.Final release of the Arquillian Core component!

Highlights in this release

@ArquillianResource URL for in-container tests

You can now inject the base URL for any deployment by using the @ArquillianResource injection point even in in-container tests.

@Deployment
public static WebArchive test() {
   return ShrinkWrap.create(WebArchive.class);
}

@Deployment(name = "X")
public static WebArchive test2() {
   return ShrinkWrap.create(WebArchive.class);
}

@ArquillianResource
private URL url;

@Test
public void should() {
   // ... inject the url to the default deployment
}

@Test
public void shouldX(@ArquillianResource @OperatesOnDeployment("X") URL url) {
   // .. inject the url from the other deployment
}

When in-container URL injection happen a callback to the client is done to lookup the URL. A clalback has a little performance hit so it’s only recommended to do this if really needed.

@ArquillianResource ServletContext for in-container tests

The Servlet Protocol now expose the current ServletContext for a in-container test execution via the @ArquillianResource injection point.

@ArquillianResource
private ServletContext context;

When running Arquillian with the Tomcat or Jetty embedded container adapters, then ServletContext injection is supported on the client side as well in the next release.

Support ENV variables to configure Arquillian

We’ve opened up to allow to configure Arquillian via ENV variables following the same schema as for System Properties. The new configuration override order is as following:

1. arquillian.xml
2. arquillian.properties
3. System properties
4. ENV

Higher the number, higher the power.

Use secure communication when invoking in-container tests

Have you ever seen invoking Arquillian tests over a public network as a risk? Then this is your lucky day! The ServletProtocolConfiguration has been changed to allow for https based communication with the target container.

<container>
   <protocol qualifier="Servlet 3.0">
      <property name="scheme">https</property>
      <property name="port">8443</property>
   </protocol>
</container>

Currently no container adapter support automatic lookup of https context metadata so you need to manually configure the https port. The host should be auto resolved tho.

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 Core
Version	1.1.9.Final view tag
Release date	2015-09-02
Released by	Aslak Knutsen
Compiled against	ShrinkWrap – 1.2.2 ShrinkWrap Descriptors – 2.0.0-alpha-7 JUnit – 4.12 TestNG – 5.14.6

Published artifacts org.jboss.arquillian.core

• org.jboss.arquillian.core » arquillian-core-api jar javadoc pom
• org.jboss.arquillian.core » arquillian-core-spi jar javadoc pom
• org.jboss.arquillian.core » arquillian-core-impl-base jar javadoc pom
• org.jboss.arquillian.config » arquillian-config-api jar javadoc pom
• org.jboss.arquillian.config » arquillian-config-spi jar javadoc pom
• org.jboss.arquillian.config » arquillian-config-impl-base jar javadoc pom
• org.jboss.arquillian.test » arquillian-test-api jar javadoc pom
• org.jboss.arquillian.test » arquillian-test-spi jar javadoc pom
• org.jboss.arquillian.test » arquillian-test-impl-base jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-spi jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-impl-base jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-test-api jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-test-spi jar javadoc pom
• org.jboss.arquillian.container » arquillian-container-test-impl-base jar javadoc pom
• org.jboss.arquillian.junit » arquillian-junit-core jar javadoc pom
• org.jboss.arquillian.junit » arquillian-junit-standalone jar javadoc pom
• org.jboss.arquillian.junit » arquillian-junit-container jar javadoc pom
• org.jboss.arquillian.testng » arquillian-testng-core jar javadoc pom
• org.jboss.arquillian.testng » arquillian-testng-standalone jar javadoc pom
• org.jboss.arquillian.testng » arquillian-testng-container jar javadoc pom
• org.jboss.arquillian.testenricher » arquillian-testenricher-cdi jar javadoc pom
• org.jboss.arquillian.testenricher » arquillian-testenricher-ejb jar javadoc pom
• org.jboss.arquillian.testenricher » arquillian-testenricher-resource jar javadoc pom
• org.jboss.arquillian.testenricher » arquillian-testenricher-initialcontext jar javadoc pom
• org.jboss.arquillian.protocol » arquillian-protocol-servlet jar javadoc pom
• org.jboss.arquillian.protocol » arquillian-protocol-jmx jar javadoc pom
• org.jboss.arquillian » arquillian-bom pom

Release notes and resolved issues 5

Enhancement

• ARQ-540 - Support @ArquillianResource URL for in-container test cases

Feature Request

• ARQ-1966 - Support ENV variables to configure Arquillian
• ARQ-1975 - Adds ServletContext as Arquillian Resource
• ARQ-1977 - Allow for setting the protocol in ServletProtocolConfiguration

Bug

• ARQ-1976 - All ResourceProvider#canProvide implementations could try to inject subtypes

Thanks to the following list of contributors: Aslak Knutsen, Radoslav Husar, Hielke Hoeve, George Gastaldi, Alex Soto, Alex Bradford

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.CR9 release of the Arquillian Container Weld Root POM 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 Container Weld Root POM
Modules	Arquillian Weld Root POM Container Adapter Arquillian Weld Container Adapter
Version	1.0.0.CR9 view tag
Release date	2015-08-26
Released by	Jozef Hartinger
Compiled against	Arquillian Core – 1.1.4.Final

Published artifacts org.jboss.arquillian.container

• org.jboss.arquillian.container » arquillian-weld-ee-embedded-1.1 jar javadoc pom
• org.jboss.arquillian.container » arquillian-weld-se-embedded-1 jar javadoc pom
• org.jboss.arquillian.container » arquillian-weld-se-embedded-1.1 jar javadoc pom

Release notes and resolved issues 2

Feature Request

• ARQ-328 - EJB-API dependencies in Weld EE container should be optional (causes failures on boot)
• ARQ-1793 - arquillian-weld-ee-embedded expose wrong version of Arquillian Core

Thanks to the following list of contributors: Jozef Hartinger, Aslak Knutsen