I haven't been able to reproduce so far. During the build run I get an error in org.jboss.forge.container.dependencies.AddonRequiredDependencyTest In the surefire log I see the following stack trace:

org.jboss.forge.container.dependencies.AddonRequiredDependencyTest  Time elapsed: 1.437 sec  <<< ERROR!
java.lang.NullPointerException
        at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:352)
        at org.jboss.forge.maven.container.MavenDependencyResolver.resolveDependencyHierarchy(MavenDependencyResolver.java:228)
        at org.jboss.forge.addon.manager.AddonManager.install(AddonManager.java:41)
        at org.jboss.forge.arquillian.ForgeDeployableContainer.deploy(ForgeDeployableContainer.java:77)
        at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
        at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
        at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
        at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
...

I guess there is a dependency problem. Note that I am not able to run the tests using:

mvn clean install -f container-tests/pom.xml

as the artifact identified by org.jboss.forge:example:jar:2.0.0-SNAPSHOT cannot be found. I assume the classifier "forge-addon" used by the artifact is not reflected within dependency declaration.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira