Download JAR files tagged by plugin with all dependencies

The Maven Help plugin provides goals aimed at helping to make sense out of the build environment. It includes the ability to view the effective POM and settings files, after inheritance and active profiles have been applied, as well as a describe a particular plugin goal to give usage information.

A Maven plugin that creates launchers for Windows (using Janel), Mac OS X (creating a .app structure, or tree with shell script) or Linux (using a shell script). (Apache License v2) 2008-2024 Matt Gumbley, DevZendo.org Note that the Universal Application Stub and Janel have separate licenses as described in their included license files.

Capture PostgreSQL database changes using Debezium integration. Note that this plugin is intended for advanced use cases and requires a proper Debezium setup as explained e.g. in [the following blueprint](https://kestra.io/blueprints/194-use-debezium-to-trigger-a-flow-whenever-new-entries-hit-a-postgres-database-then-send-notification-to-slack-and-process-data-in-python). For simple use cases, consider using the [JDBC-based PostgreSQL plugin](https://kestra.io/plugins/plugin-jdbc-postgres) instead.

PlayerShops GUI is the most playerfriendly shop plugin. Using this plugin players will be able to create their own virtual shop, where they can sell their items. They will be able to browse around in a public shop listing, check out other shops and purchase items from other players. Everything works with a intuitive inventory GUI - basically zero commands required! PlayerShops is a Genesis addon. It requires Genesis or higher in order to work.

Maven plugin for creating NetBeans modules. It defines a custom lifecycle called "nbm". During packaging, the module JAR is enhanced with NetBeans-specific manifest entries and, along with other required files, packed into a *.nbm file, ready for distribution. Additionally the plugin provides aggregator goals to create an update site or cluster for your module projects.

This plugin provides a GUI for setting the standard system properties controlling SSL/TLS connections in VisualVM. Setting the properties using the plugin is equivalent to providing the properties on the command line. However, the properties provided on the command line take precedence and if set the GUI editing is disabled. <BR> <BR> Currently the plugin supports editing these system properties: <BR> <UL> <LI><CODE>javax.net.ssl.keyStore</CODE></LI> <LI><CODE>javax.net.ssl.keyStoreType</CODE></LI> <LI><CODE>javax.net.ssl.keyStorePassword</CODE></LI> <LI><CODE>javax.net.ssl.trustStore</CODE></LI> <LI><CODE>javax.net.ssl.trustStoreType</CODE></LI> <LI><CODE>javax.net.ssl.trustStorePassword</CODE></LI> <LI><CODE>javax.rmi.ssl.client.enabledCipherSuites</CODE></LI> <LI><CODE>javax.rmi.ssl.client.enabledProtocols</CODE></LI> </UL>

checker-qual-android contains annotations (type qualifiers) that a programmer writes to specify Java code for type-checking by the Checker Framework. The checker-qual-android artifact is identical to the checker-qual artifact, except that in checker-qual-android annotations have classfile retention. The default Android Gradle plugin retains types annotated with runtime annotations in the main dex, but strips out class-retention annotations.

This plugin makes basic repository information available through maven resources. This can be used to display "what version is this?" or "who has deployed this and when, from which branch?" information at runtime, making it easy to find things like "oh, that isn't deployed yet, I'll test it tomorrow" and making both testers and developers life easier. See https://github.com/git-commit-id/git-commit-id-maven-plugin

TWiStErRob's Convention plugin for Android applications. Various utilities and setup for minimal configuration of apps. Features: * Automatic singing based on conventional names. * Automatic minification setup including common rules. * Automatic versioning based on version.properties and VCS. * Rename APK file name to contain more information. * Release artifact generation (ZIP including APK and other files).

The PDS4 LDDTool uses the Maven plugin "model-dmdocument" as an executible jar to process an input XML file. The input XML document is parsed and the contents are validated against the master database. The validated contents are integrated into the master database. The XML Schema and Schematron files are written. The process report and spreadsheet are written. Sandbox version: for experimental use only.