Download JAR files tagged by optional with all dependencies

A Maven plugin that installs the AppNeta Java instrumentation agent. Can be used within a pom or directly from command line. The supported goals are "install-agent" and "download-agent". The configuration properties are "agentVersion", "agentLocation" and "agentOperatingSystem"(the last one is only valid for "download-agent" goal), all are optional and may be specified as maven configuration properties or system properties. For other information on our Java agent please visit https://docs.appneta.com/java.

MASON is a fast discrete-event multiagent simulation library core in Java, designed to be the foundation for large custom-purpose Java simulations, and also to provide more than enough functionality for many lightweight simulation needs. MASON contains both a model library and an optional suite of visualization tools in 2D and 3D.

This project contains a logback.xml which sets up logging for brooklyn, using files supplied in the upstream brooklyn-logback-includes project. - One recommended way to configure logging on a project is to add this as an *optional* *runtime* dependency in a project's pom.xml file, so that logback.xml is on the classpath when that project is run but it is *not* exported to new/dependent projects thus allowing them to supply their own logging. - For more information see the logback.xml file in this project or the Logging section of the web site / user guide.

MASON is a fast discrete-event multiagent simulation library core in Java, designed to be the foundation for large custom-purpose Java simulations, and also to provide more than enough functionality for many lightweight simulation needs. MASON contains both a model library and an optional suite of visualization tools in 2D and 3D.

The RepeatCheckUntilVerified Utility offers a robust asynchronous mechanism for performing repeated condition checks with configurable retries, initial delays, and optional backup actions. Designed for Kotlin-based applications, it simplifies the implementation of retry logic for operations that require validation through repeated attempts, such as network requests, file I/O operations, or any condition-dependent tasks. With features like adjustable timing, maximum attempt control, and failure management through backup actions, it ensures resilience and flexibility in handling operations that may not succeed on the first try. Ideal for applications requiring high reliability and precise control over task verification processes.

The Limbus System is a small light-weight CDI framework managing the Limbus Core Components. The object graph is represented by an XML configuration file or can be build using the Limbus System API. This module delivers an optional system component that visualizes the object graph and its dependencies after initializing: com.remondis.limbus.system.visualize.LimbusSystemVisualizer This component can be added to the Limbus System. To keep the dependencies of this module transparent and light-weight, the graph renderer is declared as an optional dependency. Add the following dependencies to your project to use the visualisation component: <!-- Graph Stream for Visualization feature This is an optional dependency and only required if using the com.remondis.limbus.system.visualize.LimbusSystemVisualizer --> <dependency> <groupId>org.graphstream</groupId> <artifactId>gs-core</artifactId> <version>1.3</version> </dependency> <dependency> <groupId>org.graphstream</groupId> <artifactId>gs-ui</artifactId> <version>1.3</version> </dependency>

AutoComplete is a library allowing you to add IDE-like auto-completion (aka "code completion" or "Intellisense") to any Swing JTextComponent. Special integration is added for RSyntaxTextArea, since this feature is commonly needed when editing source code. Features include: Drop-down completion choice list. Optional companion "description" window, complete with full HTML support and navigable with hyperlinks. Optional parameter completion assistance for functions and methods, ala Eclipse and NetBeans. Completion information is typically specified in an XML file, but can even be dynamic.

The Zello Channels SDK allows you to integrate Zello push-to-talk into your own application. The SDK communicates with a Zello server over a web socket connection using a JSON-based protocol, and offers a simple API to send and receive audio, images, and text over Zello channels. Supported features include: Send voice messages from the device microphone Play incoming voice messages through the device speaker Send voice messages from your own audio code, e.g. from a file Receive voice message data with your own audio code with optional pass-through to the device speaker Send and recieve text messages Send and receive images Send the device's current location, and receive location messages from other users The protocol specification is also available if you prefer to develop your own client in-house.

This ApplicationProperties Java package provides a fast and easily configurable application.properties loader that mimics some key features of the Spring Boot application.properties loader. This package allows for multi-level overloading of properties based on a basename and optional suffix by searching the classpath, optional configurable file paths along with the JNDI server container context. The class [ApplicationPropertiesConfig](src/main/java/com/lyders/application-properties/ApplicationPropertiesConfig.java) controls the features of the overloading of properties such as the base name of the properties file, an optional suffix that allows for the loading of environment-specific or scenario-specific property files as needed. The following features are supported: * Names of properties files can be customized * Locations of properties files can be customized. The following path types are supported: * class path * file system paths * JNDI environment naming context (e.g., Servlet/JSP running under Tomcat) * Environment-specific property files can override the values in default properties files via a "suffix"