Download JAR files tagged by supported with all dependencies

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Typesafe subscription does not cover support for these modules.

The Jenkins Maven Plugin allows to use the Jenkins CLI (command line interface) from within a Maven build. It allows the execution of any command supported by the CLI, see https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI for further information. Therefore, it downloads the current jenkins-cli.jar from ${project.ciManagement.url}/jnlpJars/jenkins-cli.jar and uses that artifact for interacting with the Jenkins server. The architecture of the Jenkins Maven Plugin follows the UNIX philosophy "do one thing and do it well": it does not provide any logic for specific tasks, for instance creating job configuration files. This can be done with another, more appropriate plugin and its result can then be specified as stdin to the Jenkins Maven Plugin.

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Typesafe subscription does not cover support for these modules.

POJava DateTime is a simple, light-weight Java-based API for parsing and manipulating dates. It parses dates from most languages and formats out of the box without having to specify which format is expected. Defaults such as time zones, and whether to interpret an internationally ambiguous date like "03/06/2014" as DMY order or MDY order are inferred by system time zone and locale and stored in a default config object that can be replaced or overridden. Multiple languages for month names are supported without any additional configuration needed.

OpenCL4Java is a thin Java wrapper around OpenCL's C API. It uses JNA as its interop layer library, which means it works on all of the (many) JNA-supported platforms (see http://jna.dev.java.net/). It is autogenerated by JNAerator (http://jnaerator.googlecode.com/), so updates to newer OpenCL specs are a matter of seconds. Note that OpenCL4Java is used by JavaCL, an Object-Oriented API that presents OpenCL in a much more practical, powerful and idiomatic way to Java. For more info, please visit http://code.google.com/p/nativelibs4java/wiki/OpenCL.

This powerful reporting library aims to simplify producing reports using iText. Looking at producing reports with iText the most demanding tasks are how to get from data to report blocks, how to style those blocks and how to evaluate (debug) the resulting report. Exactly those three major tasks are well supported by the VectorPrint report library: - (combination of) xml configuration and annotations to transform existing Java data objects into report block - provide styling information (css like) seperate from code - a firebug like debug mode to help evaluate your report.

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Typesafe subscription does not cover support for these modules.

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Typesafe subscription does not cover support for these modules.

This plugin provides integration between Spring and Maven. Plugin goals support loading a Spring context XML file as part of the Maven build lifecycle. The XML file can be on the local file system or be accessible via any URL Spring's resource loading mechanism can understand. Spring's "classpath:context.xml" style notation is supported. Annotated Java classes can also be used to load a Spring context. Maven properties are injected into the Spring context (both XML and annotation style) as a java.util.Properties bean named "mavenProperties". Maven properties are also registered as a top level PropertySource so that Spring's placeholder resolution framework automatically considers them. See Project Reports -> Plugin Documentation for details on plugin goals. By default, the profile "maven" is set as an active Spring profile along with any other active Maven profiles.

This subproject provides a home to modules contributed by external developers which may or may not move into the officially supported code base over time. A module in this subproject doesn't have to obey the rule of staying binary compatible between minor releases. Breaking API changes may be introduced in minor releases without notice as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation. The Typesafe subscription does not cover support for these modules.