Download JAR files tagged by interfaces with all dependencies

This module contains a classpath scanner, and bytecode reader. It is useful in any java runtime environment, and allows java code to parse bytecode into a meta structure of classes, annotations, methods and fields. This meta structure is used throughout xapi to allow us to extend java structures in a cross-platform compliant way (exposing services and service objects so you can hack support for whatever runtime you need). It is especially useful for fast runtime injection, and as an extensible structure during codegen (which exposes mutable interfaces for our meta structure)

Siena is a persistence abstraction layer made in Java with various implementations: * siena-jdbc: persists objects into a relational database using JDBC (status: deeply tested) * siena-gae: persists objects into the Google App Engine's datastore using its low-level API (status: beta) * siena-sdb: persists objects using Amazon's SimpleDB (very experimental) * siena-remote: persists objects remotely using a remote web application that uses siena. (planning) Siena is also: * Intrusive. You make a class persistent by extending a certain class. Relationships are defined also in an intrusive way. * Simple. Simplicity is the most important thing. * Limited. Due to the simplicity there are several unsupported things such as JOINs. * Extensible. There are two interfaces you can implement on your own way.

JSci is a set of open source Java packages. The aim is to encapsulate scientific methods/principles in the most natural way possible. As such they should greatly aid the development of scientific based software. It offers: abstract math interfaces, linear algebra (support for various matrix and vector types), statistics (including probability distributions), wavelets, newtonian mechanics, chart/graph components (AWT and Swing), MathML DOM implementation, ... Note: some packages, like javax.comm, for the astro and instruments package aren't listed as dependencies (not available).

Scala classes to allow more elegant use of Multiverse from Scala. Atm the functionality is quite limited since not a lot of effort was put in the Scala integration. For the 0.6 release Multiverse should be able to work with in Scala written transactional objects configured with the Multiverse annotations. So that would reduce the need for this library, although in Scala they want to have special Scala 'interfaces' that provide some syntactic sugar to use java collections in Scala. So this module would be the good location for that. If anyone would like to help improving the Multiverse/Scala integration, please don't hesitate to join.

<b>JCAPTCHA</b>, for <b>J</b>ava <b>C</b>ompletely <b>A</b>utomated <b>P</b>ublic <b>T</b>est to tell <b>C</b>omputers and <b>H</b>umans <b>A</b>part <br/>The open source java framework for captcha definition and integration <br/> A captcha is a simple captcha container that contains a question, a challenge, and a response validation routine.<BR/> A captcha can only be built by a captcha factory that provides methods to build localized captchas.<br/> This jar aims to provide interfaces and implementation of generic and typed captcha and captcha factories.<BR/> It uses the word generator, types sub packages (image and sound) components (word to image, word to sound) to build typed captchas captchas.

Shades is an Object/Relational Mapping (ORM) framework that works in conjunction with JDBC APIs. Instead of relying on XML or annotations for configuration, Shades relies on an interface called ORMapping. This makes shades simple and flexible. Shades has no new transaction model nor Connection management which you must learn. You control the transactions, and the Connection that Shades uses, through plain JDBC interfaces. Shades is designed to work well with modern web development frameworks like Tapestry and Wicket.

Apache Spatial Information System (SIS) is a free software, Java language library for developing geospatial applications. SIS provides data structures for geographic features and associated metadata along with methods to manipulate those data structures. The library is an implementation of GeoAPI 3.0.2 interfaces and can be used for desktop or server applications. The SIS metadata module forms the base of the library and enables the creation of metadata objects which comply with the ISO 19115 international standard. The SIS referencing module enable the construction of geodetic data structures for geospatial referencing as defined by ISO 19111 standard, along with the associated operations which enable the transformation of coordinates between different reference systems. The SIS storage modules provide a common approach to the reading and writing of metadata, features and coverages applicable to simple imagery as to many dimensional data structures.

PATRIUS is a core space dynamics Java library that enables to quickly develop high level algorithms such as orbit extrapolator. PATRIUS contains several sub-libraries that work together and cover low level classes (i.e.: such as matrix, vectors, orbits parameters) as well as high level classes and interfaces (i.e.: numerical propagators, attitude laws, manoeuvers sequences). All the main domains of space dynamics are available: Analysis, algebra and geometry core library (quaternions, derivable functions, integrators …) Core objects for space dynamics (dates, orbits, frames...) Orbit propagation: analytical, semi-analytical and numerical propagators, a full set of force models Maneuvers: impulsive or continuous thrust, sequences Attitude: extensible set of attitude laws, sequences and guidance framework Events: event detection (orbital, sensor events, etc.) and post-processing (chronograms) Spacecraft: characteristics of mass, geometry (drag force), sensors field of view, etc.

This module defines the interfaces for Comparators in the TCS Alignment Toolbox. A Comparator has the purpose of defining the dissimilarity between elements in the input sequences of an Alignment. More specific information on Comparators can be found in the 'Comparator' interface. You can find a lot of helpful standard implementations of Comparators in the comparators-lib module. In the TCS Alignment Toolbox we require the output values of Comparators to lie in the range [0,1]. Many natural dissimilarities on value sets do not meet this criterion, such that additional normalization has to be applied. To that end this package also contains a Normalizer interface for functions that map real values from the range [0, infinity) to the range [0,1]. This package also provides a few convenience implementations of the Comparator interface to make the implementation of custom Comparators simpler, namely: SkipExtendedComparator, ParameterLessSkipExtendedComparator, ComparisonBasedSkipExtendedComparator, and ParameterLessComparisonBasedSkipExtendedComparator. Finally the TCS Alignment Toolbox also provides the means to learn parameters of Comparators. To enable that Comparators must implement the DerivableComparator interface to properly define the parameters that can be learned and the gradient of the dissimilarity with respect to these parameters. Gradients are stored using the Gradient interface as well as some convenience implementations of said interface, namely EmptyGradient, SingletonGradient, ArrayGradient and ListGradient.

This is a specialized version of the Clirr Maven Plugin. It adds capabilities for excluding specific error types, as well as separating code into three, rather than two, subgroups: Internal code (no checks) Externally invoked code (Annotated with an "externally invoked" annotation, same as Externally implemented, but adding methods to interfaces and abstract classes is allowed) Externally implemented code (Assumed default. Full backwards compatibility required *unless* an interface is annotated with a defined adaptor annotation, in which case full backwards compatibility is required for the adaptor class, but the rules of @ExternallyInvoked apply to the interface itself) Clirr is a tool that checks Java libraries for binary and source compatibility with older releases. Basically you give it two sets of jar files and Clirr dumps out a list of changes in the public API. The clirr-maven-plugin can be configured to break the build, if it detects incompatible api changes. In a continuous integration process, the clirr-maven-plugin can automatically prevent accidental introduction of binary or source compatibility problems. Additionally, the plugin can generate a report as part of the generated site.