Download parent JAR file with all dependencies

PureSol Technologies' commons libraries: This is a set of functionality to extend standard JDK functionality and to collect common functionality for PureSol Technologies' development projects. This library is not intended to be used by parties outside of PureSol Technologies, as changes between versions might be incompatible.

Base component of Project Casquatch

The parent pom used by projects from fathzer.com.

A JNA-based (native) operating system information library for Java that aims to provide a cross-platform implementation to retrieve system information, such as version, memory, CPU, disk, battery, etc.

PlanOut for Java - parent POM

Google Cloud Dataflow Java SDK provides a simple, Java-based interface for processing virtually any size data using Google cloud resources. This artifact includes the parent POM for other Dataflow artifacts.

Genson library parent and aggregator

A small library and taglib for accessing Maven version metadata at runtime.

logback project pom.xml file

Parent artifact for DXA

H2H-Web is a web application designed to display all entry paths for each application, monitor activity for each entry point, save each pentesting

Batch processing is a pervasive workload pattern, expressed by a distinct application organization and execution model. It is found across virtually every industry, applied to such tasks as statement generation, bank postings, risk evaluation, credit score calculation, inventory management, portfolio optimization, and on and on. Nearly any bulk processing task from any business sector is a candidate for batch processing. Batch processing is typified by bulk-oriented, non-interactive, background execution. Frequently long- running, it may be data or computationally intensive, execute sequentially or in parallel, and may be initiated through various invocation models, including ad hoc, scheduled, and on-demand. Batch applications have common requirements, including logging, checkpointing, and parallelization. Batch workloads have common requirements, especially operational control, which allow for initiation of, and interaction with, batch instances; such interactions include stop and restart.