Download JAR files tagged by checker with all dependencies

Automatic Groovy parameter checker. How to use: 1. Annotate your Groovy classes with @ParamsNotNullNotEmpty; 2. At compile time, code will be added into each of your methods to check each parameter to make sure it is not null and in the case of Collections, Maps and Strings, it is not empty; 3. At run time, if a parameter is null or empty, it will throw an IllegalArgumentException with details about the null or empty parameter. To disable the annotation at compile time, set the ParamsNotNullNotEmpty.NoOpMode flag to true.

JTidy is a Java port of HTML Tidy, a HTML syntax checker and pretty printer. Like its non-Java cousin, JTidy can be used as a tool for cleaning up malformed and faulty HTML. In addition, JTidy provides a DOM interface to the document that is being processed, which effectively makes you able to use JTidy as a DOM parser for real-world HTML.

JTidy is a Java port of HTML Tidy, a HTML syntax checker and pretty printer. Like its non-Java cousin, JTidy can be used as a tool for cleaning up malformed and faulty HTML. In addition, JTidy provides a DOM interface to the document that is being processed, which effectively makes you able to use JTidy as a DOM parser for real-world HTML.

This artifact provides the implementation of the model checker presented in the paper "M3C: Modal Meta Model Checking" (https://dx.doi.org/10.1007/978-3-030-00244-2_15) by Bernhard Steffen and Alnis Murtovi. The paper is based on "Model Checking for Context-Free Processes" (https://link.springer.com/chapter/10.1007/BFb0084787) by Olaf Burkart and Bernhard Steffen. Note that this implementation requires a runtime dependency to a specific ADDLib backend (see https://add-lib.scce.info/), which is not explicitly included in this artifact due to packaging reasons.

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