Download JAR files tagged by processor with all dependencies

Maven Anno Mojo module conatining the implementation of the MojoDescriptorExtractor used by the plugin maven-plugin-plugin. This POM override the standard java MojoDescriptorExtractor to avoid qdox parsing error. Adding this module as a dependencies to maven-plugin-plugin will stop the xdoclet plugin system is from being activated, and will activate this annotations processor instead.

Maven Anno Mojo module conatining the implementation of the MojoDescriptorExtractor used by the plugin maven-plugin-plugin. This POM override the standard java MojoDescriptorExtractor to avoid qdox parsing error. Adding this module as a dependencies to maven-plugin-plugin will stop the xdoclet plugin system is from being activated, and will activate this annotations processor instead.

objectify-query is a JSR 269 annotation processor that processes objectify-appengine's annotations to generate "safer" query classes. The generated query class provides type-safe methods to filter each of the entities indexed properties

This nifi-processor-utils module is designed to capture common patterns and utilities that can be leveraged by other processors or components to help promote reuse. These patterns may become framework level features or may simply be made available through this utility. It is ok for this module to have dependencies but care should be taken when adding dependencies as this increases the cost of utilizing this module in various nars.

'Real world' compile-time testing of the annotation processor. Its impossible/hard to fully replicate the compile time environment including annotation processing, class generation, service loading, etc.. This module contains standard and edge case classes container AndHow properties. Unit tests then check to ensure that PropertyRegistrars were generated and registered as services for each top level class containing Properties.

This module is part of the eAudit4j audit library, providing a simple and pluggable solution for auditing in Java. This particular Maven module provides a set of audit processors that persists audit events using JDBC. Depending on the processor implementation, the JDBC connection can be instantiated from a configurable database connection pool, a JNDI name, or a data source. Once persisted, the event is passed on without modification.

A fully-conforming XML Schema 1.0 processor with partial support for the XML Schema 1.1 specifications (Part 1: Structures and Part 2: Datatypes). Xerces2 also provides a complete implementation of the following W3C Recommendations: * Extensible Markup Language (XML) 1.1 * Document Object Model (DOM) Level 3 Core * Document Object Model (DOM) Level 3 Load and Save * XML Inclusions (XInclude) Version 1.0

ADIF Processor visualizes contacts in your input file on Google Earth. It generates a Google Earth Project file, also known as a KML file, with a visualization of each contact in the ADIF/SOTA CSV input file where station locations can be determined. It parses structured tags in comments to enrich the correct ADIF output file. QRZ.com is used to determine station locations and provide additional information in the ADIF output file. The markdown/text file output contains a listing of contacts. The processor contains activity databases for the main outdoor activities such as SOTA, POTA, GMA, HEMA etc.

This library is a façade for image manipulation, acting as a proxy to libraries such as Java2D, JAI, ImageJ. In its early years (after 2003) it was used for photo development, metadata management and even demonstrated distributed calculus on the Sun Grid. At the end of 2016 development stopped. It resumed at the end of 2022, dropping obsolete stuff (JAI). At the moment the portions related to image manipulation are not tested. Features about metadata manipulation are being actively developed. A few scripts for U*ix and Windows systems are provided to quickly run examples: + runViewerExample.sh + runHistogramViewerExample.sh + runViewerExample.bat + runHistogramViewerExample.bat Directory tree ============== * modules/Core sources for the core component * modules/Metadata sources for the Metadata component * modules/Processor sources for the imaging processor * modules/Renderer sources for the renderer * modules/Examples/ViewerExample example about the renderer * modules/Examples/HistogramViewerExample example about histogram computation * modules/Examples/CustomOperationExample example about custom operations * modules/Examples/Miscellaneous miscellaneous examples