Download JAR files tagged by build with all dependencies

The ConvertAPI helps converting various file formats. Creating PDF and Images from various sources like Word, Excel, Powerpoint, images, web pages or raw HTML codes. Merge, Encrypt, Split, Repair and Decrypt PDF files. And many others files manipulations. In just few minutes you can integrate it into your application and use it easily. The ConvertAPI client library makes it easier to use the Convert API from your Java 8 projects without having to build your own API calls.

The ConvertAPI helps converting various file formats. Creating PDF and Images from various sources like Word, Excel, Powerpoint, images, web pages or raw HTML codes. Merge, Encrypt, Split, Repair and Decrypt PDF files. And many others files manipulations. In just few minutes you can integrate it into your application and use it easily. The ConvertAPI client library makes it easier to use the Convert API from your Java 8 projects without having to build your own API calls.

Java, Selenium, Appium, Winium, Extend, and TestNG automated testing framework. Bichromate integrates the best of these frameworks and takes automation to the next level. With Bichromate there is one function call that builds any type of Web,IOS Mobile, Android, and Windows App driver on any platform (Windows, Mac, Linux). From Local web drivers, to SauceLabs, Browserstack, and Selenium grid. Build data driven tests is never easier. Bichromate also gives you built in Factories that, access DBs, Video Capture, FTP, POM Generation, Hilite element.

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

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.

This version uses the Mavenized 1.6/1.7 branch of Maverick. It will probably eventually become the default Maverick provider implementation, but until such a time it will be a separate module. Using this version we pull the Maverick jars from the SSHTools repository and build directly Maverick is the definitive solution for total SSH compatibility on the Java™ platform. The library is designed to support SSH1 and SSH2 using any version of the Java Development Kit from 1.1 and above, and the API is also now J2ME-ready1 in anticipation of the new breed of interconnected mobile devices Downloads and more information about Maverick may be found at http://www.sshtools.co.uk/en/j2ssh-maverick/. This library is the provider bridge for SSHAPI.

This small subproject regroup most of the stuff needed to build pmd. As some java code has been produced to reduce the use of scripts when generating the website, the build also requires a small jar, which is generated by this pom. IMPORTANT NOTE: the pmd-build.jar does not need to be recompile if you modify any ant or xslt files. You can alter the files that are in the xslt directory and directly uses the appropriate ant or java task. pmd-build should be recompiled and package (and its version incrememented) only if you modify the java code.

Oxalis integration test. Compiles and packages everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

This small subproject regroup most of the stuff needed to build pmd. As some java code has been produced to reduce the use of scripts when generating the website, the build also requires a small jar, which is generated by this pom. IMPORTANT NOTE: the pmd-build.jar does not need to be recompile if you modify any ant or xslt files. You can alter the files that are in the xslt directory and directly uses the appropriate ant or java task. pmd-build should be recompiled and package (and its version incrememented) only if you modify the java code.