Download JAR files tagged by inherits with all dependencies

This archetype will create a POM that inherits from FC TIBCO Factory parent POM. This POM will be the central configuration for all the TIBCO BusinessWorks projects of this client project. It is possible for instance to redefine here the default properties that will be used for any TIBCO BusinessWorks projects.

This archetype will create a POM that inherits from FC TIBCO Factory parent POM *OR* from the client's root POM created with 'archetype-client-root-project' archetype. This POM will be the Maven configuration for the existing TIBCO BW project. 1) you want to use the default FC TIBCO Factory parent, then replace the 'rootProjectGroupId', 'rootProjectArtifactId' & 'rootProjectVersion' by the content of 'fcFactoryGroupId', 'fcFactoryArtifactId' & 'fcFactoryVersion' respectively. 2) you want to use your own parent created with 'archetype-client-root-project', then replace 'rootProjectGroupId', 'rootProjectArtifactId' & 'rootProjectVersion' by the values of your own parent (ex: 'com.company.project', 'project-root', '1.0.0').

This is the main aggregator for all implementation code shared between modules. Each module contains one or more service interfaces, exposed statically using "X_" prefixed classes. Core modules will define their API interfaces, their static accessor, and often a "plain-jre" default implementation which can be replaced by injection override. There must be zero external dependencies in any core modules. A low-performance, low-feature default is preferred over thick, dependency-ridden shared inherits.

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.