The goal of the jconch project is to produce a reliable, safe set of implementations for common tasks in mulithreaded Java applications. The goal is to be similar in spirit to the way that Spring scraps the boilerplate for common user tasks in database work.
(If you want this stuff, vote for the issue.)
You can get notices when things happen with JConch by subscribing to the JConch mailing list. Just send an e-mail to firstname.lastname@example.org. Messages will all be prepended with [jconch], so it'll be easy to create a rule to handle them. You can also subscribe to the JConch RSS feed if you don't feel like sharing your e-mail address.
While the project started out as the Java CONCurrency Handler, it's taken on an additional meaning through an idiosyncracy. The conch has been a symbol of deciding who gets a turn to speak in meetings, probably based on its use as such in 'Lord of the Flies'. That seems very fitting for a concurrency system!
This package requires a Java5 or greater JRE. While Java5 added many low-level concurrency tools (which are used in this class), it does not provide 'grab-and-go' solutions for common concurrency problems. For instance, while it provides Semaphore and CompletionService, useful tools for development, it does not provide an actual producer/consumer framework.
As of now, all development has been done by Robert Fischer of Smokejumper Consulting. If you've got tricky concurrency problems or just generally need some expertise on Java/Groovy development, drop him a line.