Download JAR files tagged by wildfly with all dependencies

A sample JAVA EE 6 project demonstrating how to use Arquillian with Wicket Framework deployed on JBoss WildFly managed downloaded from maven repository (NEXUS for example) and unpacked with dependency plugin. WAR version (everything in a single .war file).

This fraction contains additional Camel components and data formats which are not yet packaged as individual fraction. The list of the modules is available here : https://github.com/wildfly-swarm/wildfly-swarm/blob/master/camel/components/other/module.conf

Process application that uses a shared Camunda Platform engine in a Java EE Container, e.g. JBoss Wildfly. Contains: Camunda EJB Client, Camunda CDI Integration, BPMN Process, Java Delegate as CDI bean, HTML5-based start and task forms, configuration for JPA (Hibernate), JUnit Test with in-memory engine and visual process test coverage, Maven Plugins

This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module. Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars. Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the subsystem-templates by wildfly-server-provisioning-maven-plugin.

This Maven module exists solely because wildfly-server-provisioning-maven-plugin is able to load the subsystem fragments (see src/main/resources/subsystem-templates/*) only from jars that are pulled by some WildFly module. Projects that have WildFly modules usually pack this kind of resources inside one of the modules' jars. Although we do not need a WildFly module to run any code, we need to have one just for the sake of loading the subsystem-templates by wildfly-server-provisioning-maven-plugin. Once Hawkular Accounts will have a subsystem or a WildFly module, the resources hosted here can move there.