Download JAR files tagged by solely with all dependencies

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.

This module exists solely to package all other gwt modules into a single uber jar. This makes deploying to non-mavenized targets much easier. Of course, you would be wise to inherit your dependencies individually; the uber jar is intended for projects like collide, which have complex configuration, and adding many jars would be a pain.

Design Patterns are typically encoded into Java code in an ad-hoc fashion. They are either embedded into the names of the classes or written into the Javadocs. Unfortunately it is impossible to accurately determine a pattern based solely on the class structure without knowing the intent of the code author. JPatterns is a collection of annotations that make it easy to communicate the use of (Design)Patterns within your code to your fellow developers and your future self.

BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR OTHERWISE USING THE PROGRAM , YOU AGREE THAT THE PROGRAM IS COPYRIGHTED AND LICENSED BY IBM CORPORATION, OR ITS AFFILIATE, SOLELY FOR YOUR INTERNAL USE, AND IS NOT SOLD. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF ANOTHER PERSON OR A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND THAT PERSON, COMPANY, OR LEGAL ENTITY TO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS: DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN "ACCEPT" BUTTON, OR USE THE PROGRAM; AND PROMPTLY DESTROY ALL COPIES OF THE PROGRAM AND RELATED DOCUMENTATION.

This module exists solely to package all other jre modules into a single uber jar. This makes deploying to non-mavenized targets much easier. Of course, you would be wise to inherit your dependencies individually; the uber jar is intended for projects like collide, which have complex configuration, and adding many jars would be a pain. It also allows dependent modules to discover new features, as modules graduate from labs to final, they will be added here. As you type X_, autocomplete will expose newly added services.