Java Libraries

InterpolatedProperties

co.bitcode.utils : InterpolatedProperties

Extends java.util.Properties with support for variable expansion

Last Version: 0.0.1

Release Date:

Last Version: 0.14

Release Date:

Last Version: 0.14

Release Date:

Last Version: 0.9

Release Date:

Last Version: 0.9

Release Date:

Last Version: 0.9

Release Date:

Last Version: 0.9

Release Date:

Last Version: 0.9

Release Date:

Last Version: 0.9

Release Date:

electric-test

com.sun.electric : electric-test

Electric is an integrated-circuit design system that offers IC layout, schematic editing, and even textual hardware-description languages. It offers a wide range of synthesis and analysis tools for working on the circuitry. It has many importers and exporters for interfacing to other EDA (Electronic Design Automation) systems. It even has a constraint system for managing chip layout. For more information about Electric, see www.staticfreesoft.com

Last Version: 9.01-b

Release Date:

Village

org.apache.torque : village

Common project descriptor for the Torque project

Last Version: 3.3.1

Release Date:

example-web

nl.gridshore.nosapi : example-web

This project is a java wrapper and client for the NOS open data API. The project consists of two modules. The nos-api-client, this is what you can use for your own project. The other component is the example. A basic implementation that uses the nos-api-client to show what you can do with it.

Last Version: 0.2.0

Release Date:

nos-api-client

nl.gridshore.nosapi : nos-api-client

This project is a java wrapper and client for the NOS open data API. The project consists of two modules. The nos-api-client, this is what you can use for your own project. The other component is the example. A basic implementation that uses the nos-api-client to show what you can do with it.

Last Version: 0.2.0

Release Date:

Gridshore NOS API

nl.gridshore.nosapi : gridshore-nosapi

This project is a java wrapper and client for the NOS open data API. The project consists of two modules. The nos-api-client, this is what you can use for your own project. The other component is the example. A basic implementation that uses the nos-api-client to show what you can do with it.

Last Version: 0.2.0

Release Date:

GORM

org.grails : grails-gorm

ORM library based on Groovy and Hibernate.

Last Version: 1.3.7

Release Date:

Last Version: 0.4.0

Release Date:

clojure-contrib

org.clojure : clojure-contrib

Clojure user contributions library.

Last Version: 1.2.0

Release Date:

Last Version: 0.1.0.beta3

Release Date:

JBoss Logging I18n Tools

org.jboss.logging : jboss-logging-tools

Parent POM for JBoss projects. Provides default project build configuration.

Last Version: 1.0.0.Beta4

Release Date:

CSUtils POI Library

net.sf.csutils : cs-utils-poi

A report engine for creating statistics or graphical reports using Excel.

Last Version: 1.0.4

Release Date:

Dynaspring

com.googlecode.dynaspring : dynaspring

Lisp-based DSL for the Spring Framework

Last Version: 0.6.0

Release Date:

CSUtils Groovy Library

net.sf.csutils : cs-utils-groovy

Provides a framework for accessing CentraSite from within the Groovy language. In particular, it adds support for CSQL (the CentraSite Query Language) to the Groovy template engine.

Last Version: 1.1.2

Release Date:

CentraSite Utilities Core Library

net.sf.csutils : cs-utils-core

Core Library of the CentraSite utilties. Other libraries (Importer, etc.) depend on it.

Last Version: 2.2.5

Release Date:

CentraSite Utilities Parent

net.sf.csutils : cs-utils-parent

CentraSite is a SOA governance registry/repository. The CentraSite utilities are a set of open source tools, used for application development based on CentraSite.

Last Version: 5

Release Date:

Multiverse Performace Tool

org.multiverse : multiverse-performance-tool

Multiverse is a Software Transactional Memory implementation that can be used in Java but also in other languages running on the JVM like Scala or Groovy. Essentially it is a framework that allows different STM implementation (with different featuresets or performance characteristics) to be used under the hood. The main STM implementation is multiverse-alpha..

Last Version: 0.6.2

Release Date:

Site of Multiverse

org.multiverse : multiverse-site

Multiverse documentation site

Last Version: 0.6.2

Release Date:

The Multiverse core package

org.multiverse : multiverse-core-tests

Contains the tests of core interfaces/classes of the Multiverse project. So no STM implementations. These tests are seperated from the

Last Version: 0.6.2

Release Date:

Alpha Multiverse STM engine

org.multiverse : multiverse-alpha

Contains an all in one jar that that contains the AlphaStm including the Multiverse Javaagent and the Multiverse Compiler. This is the JAR you want to include in your projects, if you do, you don't need to worry about any Multiverse dependency at all.

Last Version: 0.6.2

Release Date:

Alpha Multiverse STM engine: Unborn

org.multiverse : multiverse-alpha-unborn

Contains the main Multiverse STM Implementation: the Alpha Engine. The Alpha engine supports readonly and update transactions. It also supports the retry/or else mechanism. This not the jar you want to have in your final distribution because it isn't instrumented (hence the name unborn). The jar you eventually want to have in your distribution is the multiverse-alpha jar. What this package does, is test the instrumentation for the Javaagent. The compiletime instrumentation is tested in the multiverse-alpha package (where all tests are copied and reexecuted but now with compiletime instrumentation).

Last Version: 0.6.2

Release Date:

The Multiverse instrumentation package

org.multiverse : multiverse-instrumentation

Contains support functionality for instrumenting classes so that they can participate in stm. The actual instrumentation (that is very STM specific) is not part of this package.

Last Version: 0.6.2

Release Date:

Benchy the benchmark framework

org.multiverse : multiverse-benchy

Benchy the Benchmark framework is an application that can be used to execute benchmarks. It doesn't contain any Benchmarks itself (it isn't related to multiverse in principle).

Last Version: 0.6.2

Release Date:

google-api-client-json-rpc2

com.google.api.client : google-api-client-json-rpc2

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date:

google-api-client-javanet

com.google.api.client : google-api-client-javanet

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

google-api-client-xml-atom

com.google.api.client : google-api-client-xml-atom

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

google-api-client-json

com.google.api.client : google-api-client-json

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date:

google-api-client-auth-oauth

com.google.api.client : google-api-client-auth-oauth

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date:

google-api-client-auth

com.google.api.client : google-api-client-auth

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date:

google-api-client-appengine

com.google.api.client : google-api-client-appengine

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date:

google-api-client-apache

com.google.api.client : google-api-client-apache

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date:

Last Version: 1.2.3-alpha

Release Date:

google-api-client-xml

com.google.api.client : google-api-client-xml

A place to hold common settings for each module.

Last Version: 1.2.3-alpha

Release Date: