Download JAR files tagged by uber with all dependencies

A POM that can be extended by all POMs that use the ear packaging type. It extends the main uberpom because EAR files don't contain Java source code so we do not want to inherit all the reporting and other settings from the JAR Uber POM, which are not necessary and would just slow the build down.

Krausening is a library that allows for the externalization of property and configuration files from deployment units, such as WARs, EARs, uber JARs, etc. By ensuring that property files are external to deployment packages, these packages can be easily reused as-is to deploy to heterogeneous environments, circumventing the need to hack apart or rebuild the package to support property file modification.

Krausening is a library that allows for the externalization of property and configuration files from deployment units, such as WARs, EARs, uber JARs, etc. By ensuring that property files are external to deployment packages, these packages can be easily reused as-is to deploy to heterogeneous environments, circumventing the need to hack apart or rebuild the package to support property file modification.

The class loader to load classes, native libraries and resources from the top JAR and from JARs inside the top JAR. The top JAR very often is referred as an executable, standalone or uber JAR. The class loader looks through the hierarchy of JARs and allows nested JARs. The class loader delegates class loading to the parent class loader and successfully loads classes, native libraries and resources when it works not in a JAR environment. Taken from http://www.jdotsoft.com/JarClassLoader.php, see there for more information.

A collection of JAXP Validators and utility classes, including an uber validator which detects most types of validation and performs ISO/IEC 19757-11:2011 compliant xml-model validation. Especially note IntrinsicSchemaFactory which can be used to auto detect other SchemaFactories whilst validating a document. IntrinsicSchemaFactory supports xml-model schema association.

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.

Everything needed to run a comprehensive dev environment. Just type X_ and pick a service from autocomplete; new dev modules will be added as they are built. The only dev service not included in the uber jar is xapi-dev-maven, as it includes all runtime dependencies of maven, adding ~4 seconds to build time, and 6 megabytes to the final output jar size (without xapi-dev-maven, it's ~1MB).

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.

This is the main aggregator for all gwt submodules. All gwt-specific code resides here. Submodules should avoid inheriting from each other unless necessary. This goes for maven structure and gwt.xml structure. The super module is where our jre emulation layer and super-source live; all modules should inherit super, and a minimum of other modules. Some modules, like injection, are fulfilling an api in the core module, and should be accessed only through core service interfaces. Other modules, like reflection, are capable of being standalone inherits, but can benefit from core utilities like injection, so, two (or more) .gwt.xml modules may be provided. As XApi nears 1.0, all submodules will be routinely stitched together into an uber-jar, in order to have a single jar with a single gwt module that can provide all of the services at once. Internal projects will never use the uber jar, to help maintain modularity, but external projects that want to use more than one service will certainly prefer inheriting one artifact, instead of twelve. When distributed in uber-jar format, it will likely be necessary for either the uber jar, or just xapi-gwt-api.jar to appear before gwt-dev on your compile-time classpath. If using gwt-maven-plugin, the gwtFirstOnClasspath option may become problematic. If so, we will provide a forked gwt-plugin to make sure our compiler enhancements are included in the build process. There is also work going on to make a super-source-everything plugin, which will use maven to find source files, and generate synthetic .gwt.xml for you, as part of an effort to create a wholly unified programming environment. In addition to java-to-javascript, we intend to compile java-to-java and possibly other languages, like go; imagine implementing gwt deferred binding to eliminate cross-platform differences between server environments, or operating systems, or versions of a platform, or anywhere else a core api needs to bind to multiple implementations, depending on the runtime environment.