Download tests JAR files with dependency

All Gwt jre emulation code goes in this module, as well as any gwt-compiler overrides. xapi-gwt-api.jar must come before gwt-dev.jar on your compile classpath. A plugin is being built to automatically adjust maven runtime dependencies, but users of ant or IDEs will need to ensure the super jar comes before gwt-dev. We will petition gwt to accept our mods, but, until then, if you want bleeding edge features, you gotta do bleeding edge configuration. Code that ties directly into other modules, like java.lang.reflect for the reflection submodule, have their super-source here, and generators or other implementations in their own modules. This is to maintain consistency in what is or isn't whitelisted in XApi GWT. Some modules, like appengine, provide dependency-specific super-source in their own packages. This module is for jre, junit and core XApi services.

A jre client-side implementation of xapi-core-io. xapi-server-api will extend this functionality to servlets.

A classpath scanner that uses our fork of javassist to read classes, java sources and resources off the classpath.

The basic interfaces and services of the concurrency service.

This module contains a model interface pre-processor to generate implementation classes during maven builds.

A set of generator utils to create GWT views and editors from your data models.

All jre-specific runtime implementation for dependency injection goes in here. Note that the xapi-core-inject core library can operate without runtime support; so long as your services are correctly mapped in META-INF, you will not need runtime classpath scanning or bytecode lookup.

Some basic handling around executing processes outside of the jvm. Just a friendly reminder, This code comes with ZERO warranty.

This module contains jre default implementations of various basic utilities.

The core shared classes used by any code which needs to perform asynchronous communication.