…s with the same archive name to target the same Container
…ound and no matching container found during DeploymentGenerator validation
…iners found on classpath or problems creating the DeployableContainer instance
…pendency on jboss-parent * Formatted poms * Removed uncommented tests classified dependencies * Removed URL from child pom packaged types
… possible missconfiguration
…1 set and default configuration * Removed dependencies on container element, not supported in 1.0
Replaced by Arquillian-Showcase: https://github.com/arquillian/arquillian-showcase No containers live in Arquillian Core anymore, having examples here cause a cyclic dependency between Core and the Containers.
* ShrinkWrap 1.0.0 * ShrinkWrap Resolver 1.0.0-beta-6 * ShrinkWrap Descriptors 2.0.0-alpha-2
….isStarted In Custom container mode, Arquillian will only call setup on the container, start and stop operations are up to the user/extension to control. A container can be started and stopped between multiple TestClasses. No Managed deployments are allowed
…n Controllers to return information on backing servers * Add support for looking up different HTTPContext in ProtocolMetadata based on @Test @TargetsContainer("X") * Add support for @TargetsContainer on URL/URI @ArquillianResource injection to support named Context
… added to the repository during e.g. setup/start
* Removed some 1.6 API usage
* Fixed issue in Arquillian causing caughtInitializationException to leak between testclasses. Provoked by new test execution order in surefire 2.10?
In cases where we have the Exception class on classpath, but the Class is refering to a unknown class.
…perties -Darquillian.properties=file/claspath resource name -Darquillian.xml=file/classpath resource name -Darq.XXXX for overriding properties, see javadoc PropertiesParser
…ion in TestDeployment This opens up for more specific container/protocol type packaging for extensions.
…lianResource @OperateOnDeployment can be used in combination with @ArquillianResource for URL|URI|Context|InitialContext type injections on the client side.
…injection point Qualifier annotations are any annotation on the Field/Parameter that is not ArquillianResource. It is up to the individual ResourceProviders how they handle these.