Download JAR files tagged by packaging with all dependencies

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.

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.

The JavaFX Deploy Lib provides a core functionality for assembling JavaFX applications. It is build-tool independent and is intended to be used as a base to build plugins for Maven, Gradle and other third party tools. It is a direct replacement for the 'JavaFX packaging' library that comes with the JDK but without the limitations that come from being bundled in the JDK.

xml-commons provides an Apache-hosted set of DOM, SAX, and JAXP interfaces for use in other xml-based projects. Our hope is that we can standardize on both a common version and packaging scheme for these critical XML standards interfaces to make the lives of both our developers and users easier. The External Components portion of xml-commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson and sax.sourceforge.net; for JAXP it's Sun.

This artifact provides the implementation of the model checker presented in the paper "M3C: Modal Meta Model Checking" (https://dx.doi.org/10.1007/978-3-030-00244-2_15) by Bernhard Steffen and Alnis Murtovi. The paper is based on "Model Checking for Context-Free Processes" (https://link.springer.com/chapter/10.1007/BFb0084787) by Olaf Burkart and Bernhard Steffen. Note that this implementation requires a runtime dependency to a specific ADDLib backend (see https://add-lib.scce.info/), which is not explicitly included in this artifact due to packaging reasons.

R can use RJava or jsr223 to communicate with java. R also has a class system called R6. If you want to use a java library with native rJava or jsr223 in R there is potentially a lot of glue code needed, and R library specific packaging configuration required. However if you don't mind writing an R-centric API in Java you can generate all of this glue code using a few java annotations and the normal javadoc annotations. This plugin aims to provide an annotation processor that writes that glue code and creates a fairly transparent connection between Java code and R code, with a minimum of hard work. The focus of this is streamlining the creation of R libraries by Java developers, rather than allowing access to arbitrary Java code from R. The ultimate aim of this plugin to allow java developers to provide simple APIs for their libraries, package their library using Maven, push it to github and for that to become seamlessly available as an R library, with a minimal amount of fuss. A focus is on trying to produce CI ready libraries tested with Github workflows and ready for CRAN submission.