Download JAR files tagged by jars with all dependencies

Bridge to Babylon is a lightweight object relational mapper. The main goal of this library is simplicity. It is intended to be used with POJOs without the need of external XML mapping definition or any kind of annotation. This approache makes Bridge to Babylon the best compromize between simplicity (no xml mapping) and light library footprint: You don't use annotations so you don't have to deploy Bridge to Babylon along with your jars on remote clients.

Assembly that includes the Scriptom JAR, the JACOB JAR and its DLLs, the standard set of type library JARs, and supplemental information. This project does not include Groovy and its dependencies (since versions of Scriptom can run on different versions of Groovy). The contents of this project are included in the latest Windows Installer for Groovy, and may also be used to add full support for Scriptom to Groovy applications running on the Windows platform.

fastutil extends the Java Collections Framework by providing type-specific maps, sets, lists, and queues with a small memory footprint and fast operations; it provides also big (64-bit) arrays, sets, and lists, sorting algorithms, fast, practical I/O classes for binary and text files, and facilities for memory mapping large files. This jar (fastutil-core.jar) contains data structures based on integers, longs, doubles, and objects, only; fastutil.jar contains all classes. If you have both jars in your dependencies, this jar should be excluded.

This package contains several example programs of the usage of the Chips-n-Salsa library. Chips-n-Salsa is a Java library of customizable, hybridizable, iterative, parallel, stochastic, and self-adaptive local search algorithms. Chips-n-Salsa's source code is maintained on GitHub, and the prebuilt jars of the library can be imported from Maven Central using maven or other build tools. The purpose of the package chips-n-salsa-examples is to demonstrate usage of the major functionality of the Chips-n-Salsa library. You can find out more about the Chips-n-Salsa library itself from its website: https://chips-n-salsa.cicirello.org/.

This package contains several example programs of the usage of the JavaPermutationTools (JPT) library. JPT is a Java library that enables representing and generating permutations and sequences, as well as performing computation on permutations and sequences. It includes implementations of a variety of permutation distance metrics as well as distance metrics on sequences (i.e., Strings, arrays, and other ordered data types). In addition to programs demonstrating the usage of the JPT library, the jpt-examples package also contains programs for replicating the experiments from a few published papers that utilized the library or implementations on which the library is based. JPT's source code is maintained on GitHub, and the prebuilt jars of the library can be imported from Maven Central using maven or other build tools. The purpose of the package jpt-examples is to demonstrate usage of the major functionality of the JPT library. You can find out more about the JPT library itself from its website: https://jpt.cicirello.org/.

fastutil extends the Java Collections Framework by providing type-specific maps, sets, lists, and queues with a small memory footprint and fast operations; it provides also big (64-bit) arrays, sets, and lists, sorting algorithms, fast, practical I/O classes for binary and text files, and facilities for memory mapping large files. This jar (fastutil-core.jar) contains data structures based on integers, longs, doubles, and objects, only; fastutil.jar contains all classes. If you have both jars in your dependencies, this jar should be excluded.

A plugin helping with installing ImageJ 1.x plugins and dependencies. In ImageJ 1.x, .jar files containing an underscore are automatically scanned for classes whose names contain underscores. Every such class is considered to be a plugin. That is not true, however, for jai_codec.jar's classes. Therefore, Fiji introduced the split between plugins/ and jars/, where third-party libraries are expected to live in jars/. ImageJ2 uses the same structure since it is backwards compatible.

This version uses the Mavenized 1.6/1.7 branch of Maverick. It will probably eventually become the default Maverick provider implementation, but until such a time it will be a separate module. Using this version we pull the Maverick jars from the SSHTools repository and build directly Maverick is the definitive solution for total SSH compatibility on the Java™ platform. The library is designed to support SSH1 and SSH2 using any version of the Java Development Kit from 1.1 and above, and the API is also now J2ME-ready1 in anticipation of the new breed of interconnected mobile devices Downloads and more information about Maverick may be found at http://www.sshtools.co.uk/en/j2ssh-maverick/. This library is the provider bridge for SSHAPI.

This module exists solely to package all other jre modules into a single uber jar. This makes deploying to non-mavenized targets much easier. Of course, you would be wise to inherit your dependencies individually; the uber jar is intended for projects like collide, which have complex configuration, and adding many jars would be a pain. It also allows dependent modules to discover new features, as modules graduate from labs to final, they will be added here. As you type X_, autocomplete will expose newly added services.

This module creates two things: (1) a text file that contains a list of GAV coordinates needed for the 2nd stage boot loader (2) jar files mentioned above, in the Maven repository directory layout. Using Maven repository directory layout, as opposed to more simpler "flat directory with full of jars", allow us to share the jar files between fallback bees-driver dependencies and boot2, which saves disk space a lot. We do this in a separate module outside boot2, so that the list includes the bees-boot2 jar itself.