Download JAR files tagged by prefer with all dependencies

Bigtable connector compatible with HBase 1.x. It most of its dependencies (hbase & grpc). Its mainly intended to be used by dataflow 1.x to avoid version conflicts with grpc & protobuf. Prefer to use bigtable-hbase-1.x.

Bigtable connector compatible with HBase 2.x. It most of its dependencies (hbase & grpc). Its mainly intended to be used by dataflow 2.x to avoid version conflicts with grpc & protobuf. Prefer to use bigtable-hbase-2.x.

Yar Parent: provides yar sub-projects specific configuration and cannot be used as dependency import, prefer yar root project for that

A Java port of break_infinity.js - a solution for incremental games which want to deal with very large numbers and prefer performance over accuracy.

Please use bigtable-hbase-1.x or bigtable-hbase-1.x-hadoop. Bigtable connector compatible with HBase 1.x. It exposes the minimal set of dependencies. Its mainly intended to be used by dataflow 1.x to avoid version conflicts with grpc & protobuf. Prefer to use bigtable-hbase-1.x in general and bigtable-hbase-1.x-hadoop for hadoop classpath compatible applications.

Please use bigtable-hbase-2.x or bigtable-hbase-2.x-hadoop. Bigtable connector compatible with HBase 2.x. It exposes the minimal set of dependencies. Its mainly intended to be used by dataflow 2.x to avoid version conflicts with grpc & protobuf. Prefer to use bigtable-hbase-2.x in general and bigtable-hbase-2.x-hadoop for hadoop classpath compatible applications.

The Zello Channels SDK allows you to integrate Zello push-to-talk into your own application. The SDK communicates with a Zello server over a web socket connection using a JSON-based protocol, and offers a simple API to send and receive audio, images, and text over Zello channels. Supported features include: Send voice messages from the device microphone Play incoming voice messages through the device speaker Send voice messages from your own audio code, e.g. from a file Receive voice message data with your own audio code with optional pass-through to the device speaker Send and recieve text messages Send and receive images Send the device's current location, and receive location messages from other users The protocol specification is also available if you prefer to develop your own client in-house.

This is the main aggregator for all gwt submodules. All gwt-specific code resides here. Submodules should avoid inheriting from each other unless necessary. This goes for maven structure and gwt.xml structure. The super module is where our jre emulation layer and super-source live; all modules should inherit super, and a minimum of other modules. Some modules, like injection, are fulfilling an api in the core module, and should be accessed only through core service interfaces. Other modules, like reflection, are capable of being standalone inherits, but can benefit from core utilities like injection, so, two (or more) .gwt.xml modules may be provided. As XApi nears 1.0, all submodules will be routinely stitched together into an uber-jar, in order to have a single jar with a single gwt module that can provide all of the services at once. Internal projects will never use the uber jar, to help maintain modularity, but external projects that want to use more than one service will certainly prefer inheriting one artifact, instead of twelve. When distributed in uber-jar format, it will likely be necessary for either the uber jar, or just xapi-gwt-api.jar to appear before gwt-dev on your compile-time classpath. If using gwt-maven-plugin, the gwtFirstOnClasspath option may become problematic. If so, we will provide a forked gwt-plugin to make sure our compiler enhancements are included in the build process. There is also work going on to make a super-source-everything plugin, which will use maven to find source files, and generate synthetic .gwt.xml for you, as part of an effort to create a wholly unified programming environment. In addition to java-to-javascript, we intend to compile java-to-java and possibly other languages, like go; imagine implementing gwt deferred binding to eliminate cross-platform differences between server environments, or operating systems, or versions of a platform, or anywhere else a core api needs to bind to multiple implementations, depending on the runtime environment.