Download JAR files tagged by image with all dependencies

GroupDocs.Annotation lets you add notes to PDF and Word documents, as well as to image files – all directly from a web browser. It is a convenient web-based tool that doesn’t require any software installation and allows you and your colleagues to annotate documents online. Moreover, with GroupDocs.Annotation, you can add your notes to a document and then send it for approval or review, or share the document with others for online collaborative review in real-time. This way you get feedback faster and can keep everyone’s notes and comments in a single file.

GroupDocs.Viewer is an online document viewer that lets you read documents in your browser, regardless of whether you have the software that they were created in. You can view many types to word processing documents (DOC, DOCX, TXT, RTF, ODT), presentations (PPT, PPTX), spreadsheets (XLS, XLSX), portable files (PDF), and image files (JPG, BMP, GIF, TIFF). For each file, you get a high-fidelity rendering, showing the document just as it would if you opened it in the software it was created in. Layout and formatting is retained and you see an exact copy of the original. GroupDocs.Viewer lets you really read the document. You can search text documents, copy text and even embed the document – GroupDocs.Viewer and all - in a web page. You can print or download the file from GroupDocs.Viewer if you need to work with it offline.

JFace is a UI toolkit with classes for handling many common UI programming tasks. JFace is window-system-independent in both its API and implementation, and is designed to work with SWT without hiding it. JFace includes the usual UI toolkit components of image and font registries, text, dialog, preference and wizard frameworks, and progress reporting for long running operations. Two of its more interesting features are actions and viewers. The action mechanism allows user commands to be defined independently from their exact whereabouts in the UI. Viewers are model based adapters for certain SWT widgets, simplifying the presentation of application data structured as lists, tables or trees.

<b>JCAPTCHA</b>, for <b>J</b>ava <b>C</b>ompletely <b>A</b>utomated <b>P</b>ublic <b>T</b>est to tell <b>C</b>omputers and <b>H</b>umans <b>A</b>part <br/>The open source java framework for captcha definition and integration <br/> A captcha is a simple captcha container that contains a question, a challenge, and a response validation routine.<BR/> A captcha can only be built by a captcha factory that provides methods to build localized captchas.<br/> This jar aims to provide interfaces and implementation of generic and typed captcha and captcha factories.<BR/> It uses the word generator, types sub packages (image and sound) components (word to image, word to sound) to build typed captchas captchas.

GroupDocs.Signature for Java allows developers to write applications with ability to significantly sign electronic docs and verify them. Signatures can be of different types. API supports multitude of file formats and includes Pdf, Microsoft Office documents, Open Office formats, PowerPoint presentations, Images etc. The quite captivating fact about the API is, its UI less and independent calls can be made. It also provides a useful features to verify signed documents with stored signatures. Signature Types: - Text Signature - Image Signature - Digital Signature - Barcode Signature - QR-Code Signature - Stamp Signature Verification Types: - Text Signature - Digital Signature - Barcode Signature - QR-Code Signature For more details on the library, please visit GroupDocs website at: http://groupdocs.com/products/signature/java Note: The library comes up with some limitations in the evaluation mode. In order to test full features of GroupDocs.Signature for Java library, please request a free 30-day temporary license.

GroupDocs.Watermark for Java is a powerful document watermarking API to add image and text watermarks. Furthermore, API works to search and remove the watermarks which were already added to the documents by other third-party softwares. The watermarks added by this API are hard to remove by any third-party tools. It is straight-forward and self-descriptive for integration into the custom applications. The most notable features are: - Add text and image watermarks into documents and images - Search for possible watermarks in documents and remove them - Support various document formats: Pdf; MS Office: Word, Excel, PowerPoint, Visio - Support various image formats: png, bmp, jpeg, jpeg2000, gif, tiff, webp (including multiframe gif and tiff) - Process documents and images attached to stored email messages (msg, oft, eml, emlx formats are supported) - Add watermarks to images inside documents of all supported formats - Two ways of watermark adding/removing are supported: using generalized approach and working with supported format specifics

OpenIMAJ (Open Intelligent Multimedia in Java) is a collection of libraries and tools for multimedia analysis written in the Java programming language. OpenIMAJ intends to be the first truly complete multimedia analysis library and contains modules for analysing images, videos, text, audio and even webpages. The OpenIMAJ image and video analysis and feature extraction modules contain methods for processing visual content and extracting state-of-the-art features, including SIFT. The OpenIMAJ clustering and nearest-neighbour libraries contain efficient, multi-threaded implementations of clustering algorithms including Hierarchical K-Means and Approximate K-Means. The clustering library makes it possible to easily create visual-bag-of-words representations for images and video with very large vocabularies. The text-analysis modules contain implementations of a statistical language classifier and low-level processing pipeline. A number of modules deal with content creation, including interactive slideshows and animations. The hardware integration modules allow cross-platform integration with devices including webcams, the Microsoft Kinect, and even devices such as GPS's. OpenIMAJ also incorporates a number of tools to enable extremely-large-scale multimedia analysis using a distributed computing approach based on Apache Hadoop.

GroupDocs.Metadata for Java is a class library to process metadata associated with various Document, Image, CAD, Audio, Video and Archive formats. Key Features: - Covers most popular metadata standards: XMP, EXIF, IPTC, Image Resource Blocks, ID3, document properties - Covers most popular document formats: Microsoft Word, Microsoft Excel, Microsoft PowerPoint, PDF, Microsoft OneNote, Microsoft Visio, Open Document Format - Covers most popular image formats: BMP, GIF, DjVu, JPEG, PNG, TIFF, PSD, WebP, WMF, EMF, DICOM - Covers most popular email formats: Outlook Message, Email Message - Covers most popular audio formats: Mp3, WAV - Covers most popular video formats: Avi, Mov - Create, modify and remove metadata associated with supported document and image formats with a few lines of code - Manage EXIF metadata in Jpeg and TIFF formats - Manage XMP metadata in image and PDF formats - Manage Image Resource blocks in image formats - Manage audio metadata: ID3 tag (ID3v1, ID3v2), Lyrics3 tag, APE - Utilities to inspect and clean hidden metadata in document formats - Utilities to Search and Compare all metadata - Utilities to Export metadata to Excel/Csv - Metadata cleaner utility - MIME type detection - Read track changes. Accept or reject track changes - Read EXIF maker-notes: Sony, Nikon, Canon, Panasonic For more details on the library, please visit GroupDocs website at: https://products.groupdocs.com/metadata/Java Note: The library comes up with some limitations in the evaluation mode. In order to test full features of GroupDocs.Metadata for Java library, please request a free 30-day temporary license.

Pact server =========== The pact server is a stand-alone interactions recorder and verifier, aimed at clients that are non-JVM or non-Ruby based. The pact client for that platform will need to be implemented, but it only be responsible for generating the `JSON` interactions, running the tests and communicating with the server. The server implements a `JSON` `REST` Admin API with the following endpoints. / -&gt; For diagnostics, currently returns a list of ports of the running mock servers. /create -&gt; For initialising a test server and submitting the JSON interactions. It returns a port /complete -&gt; For finalising and verifying the interactions with the server. It writes the `JSON` pact file to disk. ## Running the server ### Versions 2.2.6+ Pact server takes the following parameters: ``` Usage: pact-jvm-server [options] [port] port port to run on (defaults to 29999) --help prints this usage text -h &lt;value&gt; | --host &lt;value&gt; host to bind to (defaults to localhost) -l &lt;value&gt; | --mock-port-lower &lt;value&gt; lower bound to allocate mock ports (defaults to 20000) -u &lt;value&gt; | --mock-port-upper &lt;value&gt; upper bound to allocate mock ports (defaults to 40000) -d | --daemon run as a daemon process -v &lt;value&gt; | --pact-version &lt;value&gt; pact version to generate for (2 or 3) -k &lt;value&gt; | --keystore-path &lt;value&gt; Path to keystore -p &lt;value&gt; | --keystore-password &lt;value&gt; Keystore password -s &lt;value&gt; | --ssl-port &lt;value&gt; Ssl port the mock server should run on. lower and upper bounds are ignored --debug run with debug logging ``` ### Using trust store 3.4.0+ Trust store can be used. However, it is limited to a single port for the time being. ### Prior to version 2.2.6 Pact server takes one optional parameter, the port number to listen on. If not provided, it will listen on 29999. It requires an active console to run. ### Using a distribution archive You can download a [distribution from maven central](http://search.maven.org/remotecontent?filepath=au/com/dius/pact-jvm-server_2.11/2.2.4/). There is both a ZIP and TAR archive. Unpack it to a directory of choice and then run the script in the bin directory. ### Building a distribution bundle You can build an application bundle with gradle by running (for 2.11 version): $ ./gradlew :pact-jvm-server_2.11:installdist This will create an app bundle in `build/2.11/install/pact-jvm-server_2.11`. You can then execute it with: $ java -jar pact-jvm-server/build/2.10/install/pact-jvm-server_2.11/lib/pact-jvm-server_2.11-3.2.11.jar or with the generated bundle script file: $ pact-jvm-server/build/2.11/install/pact-jvm-server_2.11/bin/pact-jvm-server_2.11 By default will run on port `29999` but a port number can be optionally supplied. ### Running it with docker You can use a docker image to execute the mock server as a docker container. $ docker run -d -p 8080:8080 -p 20000-20010:20000-20010 uglyog/pact-jvm-server This will run the main server on port 8080, and each created mock server on ports 20000-20010. You can map the ports to any you require. ## Life cycle The following actions are expected to occur * The client calls `/create` to initialise a server with the expected `JSON` interactions and state * The admin server will start a mock server on a random port and return the port number in the response * The client will execute its interaction tests against the mock server with the supplied port * Once finished, the client will call `/complete&apos; on the Admin API, posting the port number * The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target` * The mock server running on the supplied port will be shutdown. ## Endpoints ### /create The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter and a path. For example: POST http://localhost:29999/create?state=NoUsers&amp;path=/sub/ref/path &apos;{ &quot;provider&quot;: { &quot;name&quot;: &quot;Animal_Service&quot;}, ... }&apos; This will create a new running mock service provider on a randomly generated port. The port will be returned in the `201` response: { &quot;port&quot; : 34423 } But you can also reference the path from `/sub/ref/path` using the server port. The service will not strip the prefix path, but instead will use it as a differentiator. If your services do not have differences in the prefix of their path, then you will have to use the port method. ### /complete Once the client has finished running its tests against the mock server on the supplied port (in this example port `34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used. For example: POST http://localhost:29999/complete &apos;{ &quot;port&quot; : 34423 }&apos; This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing the pact `JSON` file to disk under the `target` directory. ### / The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently running mock servers port numbers. For example: GET http://localhost:29999/ &apos;{ &quot;ports&quot;: [23443,43232] }&apos;

Pact server =========== The pact server is a stand-alone interactions recorder and verifier, aimed at clients that are non-JVM or non-Ruby based. The pact client for that platform will need to be implemented, but it only be responsible for generating the `JSON` interactions, running the tests and communicating with the server. The server implements a `JSON` `REST` Admin API with the following endpoints. / -&gt; For diagnostics, currently returns a list of ports of the running mock servers. /create -&gt; For initialising a test server and submitting the JSON interactions. It returns a port /complete -&gt; For finalising and verifying the interactions with the server. It writes the `JSON` pact file to disk. ## Running the server ### Versions 2.2.6+ Pact server takes the following parameters: ``` Usage: pact-jvm-server [options] [port] port port to run on (defaults to 29999) --help prints this usage text -h &lt;value&gt; | --host &lt;value&gt; host to bind to (defaults to localhost) -l &lt;value&gt; | --mock-port-lower &lt;value&gt; lower bound to allocate mock ports (defaults to 20000) -u &lt;value&gt; | --mock-port-upper &lt;value&gt; upper bound to allocate mock ports (defaults to 40000) -d | --daemon run as a daemon process -v &lt;value&gt; | --pact-version &lt;value&gt; pact version to generate for (2 or 3) -k &lt;value&gt; | --keystore-path &lt;value&gt; Path to keystore -p &lt;value&gt; | --keystore-password &lt;value&gt; Keystore password -s &lt;value&gt; | --ssl-port &lt;value&gt; Ssl port the mock server should run on. lower and upper bounds are ignored --debug run with debug logging ``` ### Using trust store 3.4.0+ Trust store can be used. However, it is limited to a single port for the time being. ### Prior to version 2.2.6 Pact server takes one optional parameter, the port number to listen on. If not provided, it will listen on 29999. It requires an active console to run. ### Using a distribution archive You can download a [distribution from maven central](http://search.maven.org/remotecontent?filepath=au/com/dius/pact-jvm-server_2.11/2.2.4/). There is both a ZIP and TAR archive. Unpack it to a directory of choice and then run the script in the bin directory. ### Building a distribution bundle You can build an application bundle with gradle by running (for 2.11 version): $ ./gradlew :pact-jvm-server_2.11:installdist This will create an app bundle in `build/2.11/install/pact-jvm-server_2.11`. You can then execute it with: $ java -jar pact-jvm-server/build/2.10/install/pact-jvm-server_2.11/lib/pact-jvm-server_2.11-3.2.11.jar or with the generated bundle script file: $ pact-jvm-server/build/2.11/install/pact-jvm-server_2.11/bin/pact-jvm-server_2.11 By default will run on port `29999` but a port number can be optionally supplied. ### Running it with docker You can use a docker image to execute the mock server as a docker container. $ docker run -d -p 8080:8080 -p 20000-20010:20000-20010 uglyog/pact-jvm-server This will run the main server on port 8080, and each created mock server on ports 20000-20010. You can map the ports to any you require. ## Life cycle The following actions are expected to occur * The client calls `/create` to initialise a server with the expected `JSON` interactions and state * The admin server will start a mock server on a random port and return the port number in the response * The client will execute its interaction tests against the mock server with the supplied port * Once finished, the client will call `/complete&apos; on the Admin API, posting the port number * The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target` * The mock server running on the supplied port will be shutdown. ## Endpoints ### /create The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter and a path. For example: POST http://localhost:29999/create?state=NoUsers&amp;path=/sub/ref/path &apos;{ &quot;provider&quot;: { &quot;name&quot;: &quot;Animal_Service&quot;}, ... }&apos; This will create a new running mock service provider on a randomly generated port. The port will be returned in the `201` response: { &quot;port&quot; : 34423 } But you can also reference the path from `/sub/ref/path` using the server port. The service will not strip the prefix path, but instead will use it as a differentiator. If your services do not have differences in the prefix of their path, then you will have to use the port method. ### /complete Once the client has finished running its tests against the mock server on the supplied port (in this example port `34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used. For example: POST http://localhost:29999/complete &apos;{ &quot;port&quot; : 34423 }&apos; This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing the pact `JSON` file to disk under the `target` directory. ### / The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently running mock servers port numbers. For example: GET http://localhost:29999/ &apos;{ &quot;ports&quot;: [23443,43232] }&apos;