Download JAR files tagged by google with all dependencies

An empty artifact that Guava depends on to signal that it is providing ListenableFuture -- but is also available in a second "version" that contains com.google.common.util.concurrent.ListenableFuture class, without any other Guava classes. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-... version number is enough for some build systems (notably, Gradle) to select that empty artifact over the "real" listenablefuture-1.0 -- avoiding a conflict with the copy of ListenableFuture in guava itself. If users are using an older version of Guava or a build system other than Gradle, they may see class conflicts. If so, they can solve them by manually excluding the listenablefuture artifact or manually forcing their build systems to use 9999.0-....

This project contains artifacts that provide utility functions for Cloud Bigtable client readers and writers in Google Cloud Dataflow. Dataflow includes a different version of the cloud bigtable client, resulting in a need to have a separation of concerns and an abstraction. More importantly, there is a need for shading and renaming of packages so that Dataflow nad bigtable-hbase-dataflow's two sets of shading (needed for a variety of reasons) don't clash with each other. This submodule does package renaming which is needed for bigtable-hbase-dataflow and alleviates some issues related to developing that module.

This project contains artifacts that provide utility functions for Cloud Bigtable client readers and writers in Google Cloud Dataflow. Dataflow includes a different version of the cloud bigtable client, resulting in a need to have a separation of concerns and an abstraction. More importantly, there is a need for shading and renaming of packages so that Dataflow nad bigtable-hbase-dataflow's two sets of shading (needed for a variety of reasons) don't clash with each other. This submodule does package renaming which is needed for bigtable-hbase-dataflow and alleviates some issues related to developing that module.

JavaCL is an Object-Oriented API that makes the C OpenCL API available to Java in a very natural way. It hides away the complexity of cross-platform C bindings, has a clean OO design (with generics, Java enums, NIO buffers, fully typed exceptions...), provides high-level features (OpenGL-interop, array reductions) and comes with samples and demos. For more info, please visit http://code.google.com/p/nativelibs4java/wiki/OpenCL.

JavaCL is an Object-Oriented API that makes the C OpenCL API available to Java in a very natural way. It hides away the complexity of cross-platform C bindings, has a clean OO design (with generics, Java enums, NIO buffers, fully typed exceptions...), provides high-level features (OpenGL-interop, array reductions) and comes with samples and demos. For more info, please visit http://code.google.com/p/nativelibs4java/wiki/OpenCL.

OpenCL4Java is a thin Java wrapper around OpenCL's C API. It uses JNA as its interop layer library, which means it works on all of the (many) JNA-supported platforms (see http://jna.dev.java.net/). It is autogenerated by JNAerator (http://jnaerator.googlecode.com/), so updates to newer OpenCL specs are a matter of seconds. Note that OpenCL4Java is used by JavaCL, an Object-Oriented API that presents OpenCL in a much more practical, powerful and idiomatic way to Java. For more info, please visit http://code.google.com/p/nativelibs4java/wiki/OpenCL.

GWTUpload is a library for uploading files to web servers, showing a progress bar with real information about the process (file size, bytes transferred, etc). It uses ajax requests to ask the web server for the upload progress. It has two components written in java, the server side with servlet and utility classes, and the client side that is compiled into javascript using gwt. GWTUpload-gae is a library with aditional classes needed for using GwtUpload in Google Application Engine (GAE). JSUpload is the client library but compiled and exported into javascript, so users without Gwt skills can use it directly in their web pages. It includes a bunch of useful examples to learn how to use the library and see its features.

Spring JdbcTemplate did very convient and useful, but it also has some disadvantages or in another word “inconvenient”. For example, you can’t just pass an object and tell JdbcTemplate to turn it into a sql and save to database just like hibernate does. Alright, you may say “JdbcTemplate doesn’t need you to write hbm.xml , so it’s understandable”. But is it true that this thing is impossible to achieve? And also you know JdbcTemplate can auto turn the result of a query to a list of persistent object a.k.a PO, but when you want to do this you will meet a problem: “How to ?”.Because you can’t find any function of JdbcTemplate to pass a sql and a PO class as we expected. After you google for it, you’ve been told you can create a BeanPropertyRowMapper to deal with this. But isn’t it could be more easier? Based on those questions I create JdbcTemplateTool which can provide these features.

liveSense WRO4J framework. WRO4J is Free and Open Source Java project which brings together almost all the modern web tools: JsHint, CssLint, JsMin, Google Closure compressor, YUI Compressor, UglifyJs, Dojo Shrinksafe, Css Variables Support, JSON Compression, Less, Sass, CoffeeScript and much more. In the same time, the aim is to keep it as simple as possible and as extensible as possible in order to be easily adapted to application specific needs.

The goal of quality-test is to provide a small Java library for basic code quality checks within unit tests. It is discouraged to use quality-test in production code. The checks provided in this library are designed to be used in unit-tests. The checks and utilities provided in this package check static properties of classes, for example whether classes are marked final or constructors are private. Additionally, there are utils to give additional code coverage for private constructors. Quality-Test often can be used together with Google Reflections (http://code.google.com/p/reflections/) to perform checks such as, assure that every class in package *.dto.* is final or make sure that no class in the package *.controller.* contains any non-final static variables.