Download JAR files tagged by implementations with all dependencies

Small Java library for generating dynamic proxies on top of [ByteBuddy](https://github.com/raphw/byte-buddy) or [Javassist](https://github.com/jboss-javassist/javassist). You can generate data transfer objects, rich traits or even whole implicit DAO implementations dynamically at runtime easily. This library solves the complex stuff, so you can focus on application logic. Serializability, cloning are already solved by us. We also aim for transparent and easily debuggable proxies, because as we know proxies is usually part of "magic" for the team. Hence, the name of this library - Proxycian as a magician for the proxies ;)

Brownies Collections complements the Java Collections Framework. GapList combines the strengths of both ArrayList and LinkedList. BigList is a list optimized for storing large number of elements. There are specialized List implementations for all primitive data types (IntGapList, IntBigList, IntObjGapList, IntObjBigList). The key collection classes offer support for keys and constraints for lists and collections (KeyList, KeyCollection, KeySet, Key1List, Key1Collection, Key1Set, Key2List, Key2Collection, Key2Set).

ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them ,which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed.

1) This module contains various Zookeeper recipe implementations. 2) The recipe directory name should specify the name of the recipe you are implementing - eg. zookeeper-recipes-lock. 3) It would be great if you can provide both the java and c recipes for the zookeeper recipes. C recipes go in to zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/c Java implementation goes into zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/java. 4) The recipes hold high standards like our zookeeper c/java libraries, so make sure that you include some unit testing with both the c and java recipe code. 5) Also, please name your c client public methods as zkr_recipe-name_methodname (eg. zkr_lock_lock in zookeeper-recipes-lock/src/c) 6) To run the c tests in all the recipes, - make sure the main zookeeper c libraries in zookeeper-client-c are compiled. Run autoreconf -if;./configure; make. The libraries will be installed in {top}/src/c/.libs. - run autoreconf if;./configure;make run-check in zookeeper-recipes/$recipename/src/c

The main module contains the GeoTools public interfaces that are used by other GeoTools modules (and GeoTools applications). Where possible we make use industry standard terms as provided by OGC and ISO standards. The formal GeoTools public api consists of gt-metadata, jts and the gt-main module. The main module contains the default implementations that are available provided to other GeoTools modules using our factory system. Factories are obtained from an appropriate FactoryFinder, giving applications a chance configure the factory used using the Factory Hints facilities. FilterFactory ff = CommonFactoryFinder.getFilterFactory(); Expression expr = ff.add( expression1, expression2 ); If you find yourself using implementation specific classes chances are you doing it wrong: Expression expr = new AddImpl( expression1, expressiom2 );