Arquillian OSGi 2.1.0.CR4 Released

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

The Arquillian team is proud to announce the 2.1.0.CR4 release of the Arquillian OSGi component!

What is Arquillian OSGi?

ShrinkWrap is the simplest way to create archives in Java. Using the fluent and intuitive ShrinkWrap API, developers may assemble JARs, WARs, and EARs to be deployed directly by Arquillian during testing.

Release details

Component Arquillian OSGi
Modules
Version 2.1.0.CR4 view tag
Release date 2013-11-30
Released by Thomas Diesler
Compiled against

Published artifacts org.jboss.arquillian.protocol

  • org.jboss.arquillian.protocol » arquillian-protocol-osgi jar javadoc pom
  • org.jboss.arquillian.testenricher » arquillian-testenricher-osgi jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-osgi jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-jbosgi-embedded jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-felix-embedded jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-karaf-embedded jar javadoc pom

Thanks to the following list of contributors: Thomas Diesler

Arquillian Extension JRebel 1.0.0.Alpha1 Released

The Arquillian team is proud to announce the 1.0.0.Alpha1 release of the Arquillian Extension JRebel component!

It’s great that we can write integration tests and that Arquillian can automatically deploy them into a container. However, writing these tests arn’t always that great. It takes precious time to wait for redeploys and often you need to fix datasets (for persistence extension), test logic or the implementation.

The JRebel extension is meant to save developers time. It leverages JRebel to hot deploy classes you have changed. The IDE takes care of recompiling the modified class and all you need to do is rerun the test.

How does JRebel extension avoid redeploys?

It creates a special metadata file for each deployment in target/jrebel-temp directory. When you run your tests it checks for this file. If the file is present then no redeploy happens.

How do I enable the JRebel extension for Arquillian?

All you need to do is add arquillian-jrebel-impl to class path (i.e. as a Maven dependency) and configure your contianer to run with the JRebel agent (I assume you have JRebel installed).

Here is an example configuration for JBoss AS7 bin/standalone.conf:

JAVA_OPTS="-javaagent:%JREBEL_HOME%/jrebel.jar $JAVA_OPTS"

Do I need rebel.xml?

Not neccesarily. Arquillian JRebel Extension can automatically generate rebel.xml based on your archives content. (Note that in cases where you add new class or resource to the archive after deployment: JRebel will most likely not pick it up).

You may of course provide your own rebel.xml and add it to testable archive with ShrinkWrap. If a rebel.xml file is found, the Arquillian JRebel Extension will skip generating it’s own.

Further reading

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 Extension JRebel
Version 1.0.0.Alpha1 view tag
Release date 2013-11-26
Released by Aslak Knutsen
Compiled against

Published artifacts org.jboss.arquillian.extension

  • org.jboss.arquillian.extension » arquillian-jrebel-impl jar javadoc pom

Release notes and resolved issues 5

Feature Request
  • ARQ-892 - Should be able to reference the real disk resources in rebel.xml where applicable
  • ARQ-893 - Should be able to work with EAR, WAR and JARs with rebel.xml files pr module
  • ARQ-894 - Allow developer to provide their own rebel.xml
Bug
  • ARQ-1311 - NPE when using @Deployment(testable=false)

Thanks to the following list of contributors: Bernard Labno, Aslak Knutsen

Arquillian OSGi 2.1.0.CR3 Released

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

The Arquillian team is proud to announce the 2.1.0.CR3 release of the Arquillian OSGi component!

What is Arquillian OSGi?

ShrinkWrap is the simplest way to create archives in Java. Using the fluent and intuitive ShrinkWrap API, developers may assemble JARs, WARs, and EARs to be deployed directly by Arquillian during testing.

Release details

Component Arquillian OSGi
Modules
Version 2.1.0.CR3 view tag
Release date 2013-11-26
Released by Thomas Diesler
Compiled against

Published artifacts org.jboss.arquillian.protocol

  • org.jboss.arquillian.protocol » arquillian-protocol-osgi jar javadoc pom
  • org.jboss.arquillian.testenricher » arquillian-testenricher-osgi jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-osgi jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-jbosgi-embedded jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-felix-embedded jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-karaf-embedded jar javadoc pom

Thanks to the following list of contributors: Thomas Diesler

Arquillian OSGi 2.1.0.CR2 Released

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

The Arquillian team is proud to announce the 2.1.0.CR2 release of the Arquillian OSGi component!

What is Arquillian OSGi?

ShrinkWrap is the simplest way to create archives in Java. Using the fluent and intuitive ShrinkWrap API, developers may assemble JARs, WARs, and EARs to be deployed directly by Arquillian during testing.

Release details

Component Arquillian OSGi
Modules
Version 2.1.0.CR2 view tag
Release date 2013-11-23
Released by Thomas Diesler
Compiled against

Published artifacts org.jboss.arquillian.protocol

  • org.jboss.arquillian.protocol » arquillian-protocol-osgi jar javadoc pom
  • org.jboss.arquillian.testenricher » arquillian-testenricher-osgi jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-osgi jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-jbosgi-embedded jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-felix-embedded jar javadoc pom
  • org.jboss.arquillian.container » arquillian-container-karaf-embedded jar javadoc pom

Thanks to the following list of contributors: Thomas Diesler

ShrinkWrap Resolver 2.0.1 Released

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

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

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.0.1 view tag
Release date 2013-11-18
Released by Karel Piwko
Compiled against
  • JUnit – 4.8.2

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-maven jar javadoc pom
  • org.jboss.shrinkwrap.resolver » shrinkwrap-resolver-depchain 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 7

Enhancement
  • SHRINKRES-96 - Separate lifecycle for build-resources package
  • SHRINKRES-153 - MavenResolverSystemImpl should implement MavenWorkingSessionContainer
Feature Request
  • SHRINKRES-99 - Add support for applying includes/excludes when defining package resource
Bug
  • SHRINKRES-154 - Nonclear description in README.asciidoc for system environment properties
  • SHRINKRES-155 - MavenImporter flattens structure of resources
  • SHRINKRES-156 - org.jboss.shrinkwrap.resolver.impl.maven.pom.ParsedPomFileImpl.getVersion() returns artifactId
Task

Thanks to the following list of contributors: Karel Piwko, Andrew Lee Rubinger, Michal Matloka, Tomas Hradec, Marek Novotný