Download JAR files tagged by classes with all dependencies

This module allows you to enable suppressions for turning off warnings about Restricted APIs. !!!WARNING!!! Classes are marked as @Restricted for a reason and this module should not be used lightly! It implies that the author does not intend for them to be used outside their defined scope and as such they may be changed/modified/removed at any stage without warning. A simple upgrade of the dependency may break your module. Use at your own risk. You should try to not use @Restricted classes in the first place, but if you _must_ use them, this is a less-brutal approach than just disabling the access-modifier-checker entirely

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-....

A plugin helping with installing ImageJ 1.x plugins and dependencies. In ImageJ 1.x, .jar files containing an underscore are automatically scanned for classes whose names contain underscores. Every such class is considered to be a plugin. That is not true, however, for jai_codec.jar's classes. Therefore, Fiji introduced the split between plugins/ and jars/, where third-party libraries are expected to live in jars/. ImageJ2 uses the same structure since it is backwards compatible.

The Interaction Model Mapper enables a code-first approach to the development of a skill by abstracting the interaction model. Alexa types such as Intents and Slots are defined as Java classes, and corresponding interaction model data such as sample utterances, prompts, synonyms, etc. are stored in resource bundles. A skill is then constructed from a collection of these entities, and the interaction model is rendered from the CLI. This abstraction enables developers to componentize and share parts of their skill with others and promotes a standard software build/deploy lifecycle for skills.

Some libraries from Matthew Johnson: http://www.matthew.ath.cx/projects/java/ Modifications: - including precompiled native C libraries (libunix-java) for architectures: arm, amd64 and i386 - UnixSocket/UnixServerSocket now implements closable (allows try-with-resources usage) - Cleaned up code style - Split test classes to test classpath - Introduced JUnit - Removed the whole CGI package, it should never ever been used these days

A simple meta-classifier that uses a clusterer for classification. For cluster algorithms that use a fixed number of clusterers, like SimpleKMeans, the user has to make sure that the number of clusters to generate are the same as the number of class labels in the dataset in order to obtain a useful model. Note: at prediction time, a missing value is returned if no cluster is found for the instance. The code is based on the 'clusters to classes' functionality of the weka.clusterers.ClusterEvaluation class by Mark Hall.

A collection of scala and java classes for some basic character level processing for the Sanskrit and other Indic (kannada, telugu, etc..) languages, contributed by the open source sanskrit-coders projects and friends. Some notable facilities: * Transliterate text from one script or encoding scheme to another. * Some grammar simulation. Examples: see https://github.com/sanskrit-coders/indic-transliteration Contributions and suggestions are invited at https://github.com/sanskrit-coders/indic-transliteration . (Sister projects there may also be of interest.)

This module contains library classes for accessing the ThreadFix REST API. The ThreadFix IDE plugins use this library to retrieve application and vulnerability marker information, and in the ThreadFix scanner plugins to get endpoint information and upload scans to ThreadFix applications. The easiest way to start using the library is with the PluginClient or ThreadFixRestClient classes. Both have constructors that take a PropertiesManager instance, which holds the ThreadFix API key and url information. The default PropertiesManager implementation stores these properties in threadfix.properties, but the ThreadFix plugins extend the default PropertiesManager class to override this behavior for the target platform.

A collection of scala and java classes for some basic natural language processing (NLP) for the Sanskrit language, contributed by the open source SanskritNLP project and friends. Some notable facilities: * Transliterate text from one script or encoding scheme to another. * Deal with babylon dictionaries. * Use bots to write to wiki projects (wiktionary, wikisource etc..). * Basic metre identification. * Some grammar simulation. Contributions and suggestions are invited at https://github.com/sanskrit-coders/sanskritnlpjava . (Sister projects there may also be of interest.)

Tinder is a Java based XMPP library, providing an implementation for XMPP stanzas and components. Tinders origins lie in code that's shared between Jive Software's Openfire and Whack implementations. The implementation that's provided in Tinder hasn't been written again from scratch. Instead, code has been moved from the original projects into Tinder, preserving al of the existing features and functionality. Most of the code that's now in Tinder is based on the org.xmpp package implementation that previously existed in Openfire and Whack. This is the code that defines classes such as Packet, JID, IQ, Component and their extensions. Additionally, some multi-purpose code (such as the DataForm and Result Set Management implementations have been moved to Tinder as well.