Download JAR files tagged by manually with all dependencies

Provides a testing framework for support classes that are generated when using fluid entities. Since E.class and SuperMapper.class are not available at this point we resort to a bit of trickery so we can at least test the utility classes. fluid-core will pick up /src/test/java/com/artemis/ as resources (see /target/classes/fluid-entity-sources/) FluidGenerator can be made to deploy these while generating E and SuperMapper. See fluid-core pom which files are packaged as resources. Add new files to be deployed to FluidGenerator.generate manually!

Provides a testing framework for support classes that are generated when using fluid entities. Since E.class and SuperMapper.class are not available at this point we resort to a bit of trickery so we can at least test the utility classes. fluid-core will pick up /src/test/java/com/artemis/ as resources (see /target/classes/fluid-entity-sources/) FluidGenerator can be made to deploy these while generating E and SuperMapper. See fluid-core pom which files are packaged as resources. Add new files to be deployed to FluidGenerator.generate manually!

The goal of this module is to be able to deploy all the db driver jars to all environments instead of needing to change parent pom properties and rebuilding for each environment. The same effect used to be accomplished by manually updating all related poms with hardcoded dependencies, this module allows for just one place to be updated and the change propogates to all the packaged modules/portlets.

Stream processing like Java 8 streams, but works with Java 6 and have slightly different design. * Chicory-stream provides sequential-only streams, no parallel support. * Chicory-stream allows easy forking and reuse of streams, unlike Java 8 where stream can be used only once. * Chicory-stream automatically and transparently opens and closes resources each time stream is used, unlike Java 8 where stream should be manually closed. Part of chicory.

As a programmer did you have the experience that when you comes to implement a search page you can only transform the search form into sql manually? If your project have 20 search page like that then you have to write 20 times to implement the sql query. It’s boring and anxious. form-sql-builder-mysql is designed for ease the burden for you. It can help you to transform search or list form sent from browser into query sql automatically.

This generates a schema artifact which contains all of the schemas from xmpp.org's subversion repository. Generating this artifact enables a schema to be referenced by jaxb using the ClassPathCatalogResolver and a catalog file. To refresh the content of this artifact, either remove the src/main/resources directory manually or run a clean build from hudson. This is because maven-scm-plugin is set to checkout only if that directory does not exist so that the remote subversion repository is not hit every time a build is performed.

This is the parent module for all components of the Djenni framework - a test data generation framework that sets out to introduce better practices in test data management and generation. The core goals are: - to reduce the amount of time developers and testers spend manually crafting data - to make tests clearer by only focusing on the key data elements - to make tests even more complete by fuzzing data elements that are not deemed key to the test - to better support later test phases by helping developers to provide data generators suitable for large scale data generation in a thread safe / multi-threadable manner.

An empty artifact that Guava depends on to signal that it is providing ListenableFuture -- but is also available in a second "version" that contains com.google.common.util.concurrent.ListenableFuture class, without any other Guava classes. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-... version number is enough for some build systems (notably, Gradle) to select that empty artifact over the "real" listenablefuture-1.0 -- avoiding a conflict with the copy of ListenableFuture in guava itself. If users are using an older version of Guava or a build system other than Gradle, they may see class conflicts. If so, they can solve them by manually excluding the listenablefuture artifact or manually forcing their build systems to use 9999.0-....