Download JAR files tagged by check with all dependencies

The JAX-SB Generator is a comprehensive framework to facilitate the use of XML in software languages such as Java. This framework intends to provide tools that will allow a developer to easily integrate XML interoperability, bind XML Schemas, and analyze XML Schemas for use with any software. Currently there is only one language and one application that is supported: XML Binding in Java. Next on the agenda is the development of analysis tools for XML Schema Documents. For instance, imagine a tool that will allow you to determine whether an XSD complies to best-practices. This tool will: 1) produce warnings for structures that do not comply to best-practices, 2) tell the developer whether the logical structure can be transformed linearly to a form that complies to best-practices, and 3) to automatically produce an XSD that maintains the logical structure of the original document but now fully complies to best-practices. This is just one of many tools that will be available shortly. In the meantime, check out the binding application.

1) This module contains various Zookeeper recipe implementations. 2) The recipe directory name should specify the name of the recipe you are implementing - eg. zookeeper-recipes-lock. 3) It would be great if you can provide both the java and c recipes for the zookeeper recipes. C recipes go in to zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/c Java implementation goes into zookeeper-recipes/zookeeper-recipes-[recipe-name]/src/java. 4) The recipes hold high standards like our zookeeper c/java libraries, so make sure that you include some unit testing with both the c and java recipe code. 5) Also, please name your c client public methods as zkr_recipe-name_methodname (eg. zkr_lock_lock in zookeeper-recipes-lock/src/c) 6) To run the c tests in all the recipes, - make sure the main zookeeper c libraries in zookeeper-client-c are compiled. Run autoreconf -if;./configure; make. The libraries will be installed in {top}/src/c/.libs. - run autoreconf if;./configure;make run-check in zookeeper-recipes/$recipename/src/c

Lilith is a logging and access event viewer for the Logback logging framework. It has features comparable to Chainsaw, a logging event viewer for log4j. This means that it can receive logging events from remote applications using Logback as their logging backend. It uses files to buffer the received events locally, so it is possible to keep vast amounts of logging events at your fingertip while still being able to check only the ones you are really interested in by using filtering conditions.

This project provides the best of maven easily consumable a maven parent project, called MavenParent. With this project you get: Checkstyle and PMD checks that will work by default in eclipse with m2e-code-quality. OWASP vulnerability checks of your dependencies. Easy application of BSD-3 clause license to all your code with mycila-license plugin. The ability to easily enforce semantic version on a jar project with japicmp. Prevent duplicates on your classpath with basepom's duplicate-finder. All of the above can be configured or disabled easily with properties, just check their docs, except takari. A whole slew of pretty maven reports including the above are generated in the maven site. The ability to easily deploy to oss nexus, and publish maven generated sites back to github's sites pages.

<p>Integrate the Mantis bugtracker system into netbeans</p> <p>Note for installation - to make the "Add patch" and "Checking" comment functions work correctly the mantis system has to configured correctly please check these options, if you encounter problems:</p> <ul> <li>source_control_notes_view_status (default private, integer value 10 -> public)</li> <li>source_control_set_resolution_to (integer value 80->resolved, 90->closed)</li> <li>source_control_set_status_to (20->fixed)</li> </ul> <p>If a self-signed SSL certificate or an invalid certificate need to be accepted, please install the module "SSL Certificate Exception".</p>

Adds promotheus statistics export and collection for akka http routes. The library collects http result codes, timings, and requests in flight. It additionally optionally exposes some basic akka statistics.

This is an open source library that allows generating performance indicators easily for java based application. This library is configurable through an xml file (similar to log4j) in order to define the performance object types, dimensions, counters, the output format and statistics generation periodicity. Those statistics can be saved as a file (xml/json) or injected directly in a database. Then they can be correlated and analyzed through any Business Intelligence solution in order to check the application performance and quality: number of transactions, ratio of successful and failure ...

The goal of quality-test is to provide a small Java library for basic code quality checks within unit tests. It is discouraged to use quality-test in production code. The checks provided in this library are designed to be used in unit-tests. The checks and utilities provided in this package check static properties of classes, for example whether classes are marked final or constructors are private. Additionally, there are utils to give additional code coverage for private constructors. Quality-Test often can be used together with Google Reflections (http://code.google.com/p/reflections/) to perform checks such as, assure that every class in package *.dto.* is final or make sure that no class in the package *.controller.* contains any non-final static variables.

The goal of quality-check is to provide a small Java library for basic runtime code quality checks. It provides similar features to org.springframework.util.Assert or com.google.common.base.Preconditions without the need to include big libraries or frameworks such as Spring or Guava. The package quality-check tries to replace these libraries and provide all the basic code quality checks you need. The checks provided here are typically used to validate method parameters and detect errors during runtime. To detect errors before runtime we use JSR-305 Annotations. With these annotations you are able to detect possible bugs earlier. For more informations look at FindBugs™ JSR-305 support.

The goal of quality-check is to provide a small Java library for basic runtime code quality checks. It provides similar features to org.springframework.util.Assert or com.google.common.base.Preconditions without the need to include big libraries or frameworks such as Spring or Guava. The package quality-check tries to replace these libraries and provide all the basic code quality checks you need. The checks provided here are typically used to validate method parameters and detect errors during runtime. To detect errors before runtime we use JSR-305 Annotations. With these annotations you are able to detect possible bugs earlier. For more informations look at FindBugs™ JSR-305 support.