Download JAR files tagged by maven with all dependencies

This plugin provides integration between Spring and Maven. Plugin goals support loading a Spring context XML file as part of the Maven build lifecycle. The XML file can be on the local file system or be accessible via any URL Spring's resource loading mechanism can understand. Spring's "classpath:context.xml" style notation is supported. Annotated Java classes can also be used to load a Spring context. Maven properties are injected into the Spring context (both XML and annotation style) as a java.util.Properties bean named "mavenProperties". Maven properties are also registered as a top level PropertySource so that Spring's placeholder resolution framework automatically considers them. See Project Reports -> Plugin Documentation for details on plugin goals. By default, the profile "maven" is set as an active Spring profile along with any other active Maven profiles.

HermiT is reasoner for ontologies written using the Web Ontology Language (OWL). Given an OWL file, HermiT can determine whether or not the ontology is consistent, identify subsumption relationships between classes, and much more. This is the maven build of HermiT and is designed for people who wish to use HermiT from within the OWL API. It is now versioned in the main HermiT version repository, although not officially supported by the HermiT developers. The version number of this package is a composite of the HermiT version and an value representing releases of this packaged version. So, 1.3.7.1 is the first release of the mavenized version of HermiT based on the 1.3.7 release of HermiT. This package includes the Jautomata library (http://jautomata.sourceforge.net/), and builds with it directly. This library appears to be no longer under active development, and so a "fork" seems appropriate. No development is intended or anticipated on this code base.

This module creates two things: (1) a text file that contains a list of GAV coordinates needed for the 2nd stage boot loader (2) jar files mentioned above, in the Maven repository directory layout. Using Maven repository directory layout, as opposed to more simpler "flat directory with full of jars", allow us to share the jar files between fallback bees-driver dependencies and boot2, which saves disk space a lot. We do this in a separate module outside boot2, so that the list includes the bees-boot2 jar itself.

The JSP TLD Maven Plugin is used to automate the management of JSP Tag Library Descriptors as part of a Maven build. It is intended to decrease the burden on JSP developers associated with writing custom JSP Tag Libraries. The goal is to encourage JSP developers to write better JSP files by using custom JSP Tag Libraries more extensively. The Plugin can process Java annotations on Tag implementation classes and also discover Tag Files (.tag and .tagx files). The Java 5 Annotations recognized by this Plugin are all part of the <a href="../squeakysand-jsp/apidocs/com/squeakysand/jsp/tagext/annotations/package-summary.html">com.squeakysand.jsp.tagext.annotations</a> package.

Automated management of Jenkins jobs via Maven. Much of the information needed by Jenkins when creating a job is already in the Maven pom. The SCM information and CI url are present. Jenkins jobs also typically have names that reflect the groupId, artifactId, and version in some manner. This plugin automates the process of creating Jenkins jobs by harvesting information from the POM to create XML config files in the format Jenkins needs. The Jenkins CLI API is then used to create, update, read, and delete Jenkins jobs on the CI server. If your Jenkins instance requires authentication, add your public key to your user account on the Jenkins server.

This plugin gives SQuirreLSQL client the ability to configure alternate LaFs provided by the plugin as well as others that the user can provide. All dependencies listed with a groupId of net.sf.squirrel-sql and artifactId starting with squirrelsql-lf- are externally available open-source look and feels whose project maintainers have decided to not use maven, or those which were built and maintained only before the introduction of maven. Maven's central repository policy requires any pom that is deployed there to reference only artifacts which are also hosted in central. And a project may only use the groupId that is related to that project. So, this only leaves us with one option which is to host these external third-party artifacts using our groupId. The hope is that someday these projects will start using maven and the need for this will no longer be.

A Maven Mojo to download and "degenerate" non-maven projects into sources and binaries This MOJO is supposed to scrape and "de-generate" a zip file containing jars into a project's generated-sources folder, skipping items provided in the `src/` folder. It is intended to "mavenize-with-changes" an existing project and allow the user (of the Mojo) to replace classes which they do not have the ability/desire to recompile without setting up a full build. It can also be used to import non-maven projects by not changing anything. The itch I wanted to scratch was mostly to port libGDX to Maven, while replacing the native methods on Matrix4, without rebuilding the whole project. In essence - it's an alternative to patching someone else's project.

Jetty context XML configuration plugin generator helper. This plugin helps you to generate your Context XML file with a dynamic content such as: * classpath entries * web app resources * maven properties Plugin needs a template Jetty context XML file where the dynamic content is injected. Injection of dynamic content is supported as: * altering the DOM with new values * with enabled filtering dynamic values can be replaced as properties (see bellow) Filtering of the template file is supported. Basically it means you can include content from your maven properties in your context XML file. If desired plugin sets two maven properties with the dynamic content: * jetty.conf-plugin.classpath * jetty.conf-plugin.webapp These properties might be used for filtering as well. Plugin resolves project dependency artifacts. These artifacts are transformed into webapp resources and classpath entries. Works with multi-module projects. Works in Eclipse with enabled m2e.