Lets you build an executable jar with Maven2, containing all dependencies.
You can do that with the assembly plugin too, but that will just unpack all dependencies together with your classes in one directory and then repack that directory into a new jar. Doing it that way means files will overwrite each other if they have the same names in the same path, which is quite common with resources such as log4.properties and even other more important files.
With onejar-maven-plugin, you'll instead get a nice clean super jar with the dependency jars inside.
The Animal Sniffer Plugin is used to build signatures of APIs and to check your classes against previously generated signatures. This plugin is called animal sniffer because the principal signatures that are used are those of the Java Runtime, and since Sun traditionally names the different versions of its Java Runtimes after different animals, the plugin that detects what Java Runtime your code requires was called "Animal Sniffer".
Cloud Tools is a set of tools for deploying, managing and testing Java EE applications on Amazon's Elastic Computing Cloud (EC2) and VMware environments. There are three main parts to Cloud Tools:
* EC2Deploy - the core framework. This framework manages virtual instances (e.g. EC2), configures MySQL, Tomcat, Terracotta and Apache and deploys the application. See this blog entry for an overview.
* Maven and Grails plugins that use EC2Deploy to deploy an application
* Amazon Machine Images (AMIs) that are configured to run Tomcat and work with EC2Deploy. See list of installed software.
1.1. Docbook and maven
I was looking for a maven plugin that produces documentation with syntax highlighting from docbook .
1.2. For the impatient
This article has been written in docbook , and generated via maven with the docbkx maven plugin .
You can check it out
*
as multi pages html
*
as a single html page
*
in PDF
You can download a ready-to-build maven project here http://www.springfuse.com/blog/docbook/docbook-1.0.0-src.zip . It is ready to be customized for your needs.
sbt is a simple build tool for Scala projects that aims to do the basics well. It requires Java 1.5 or later.
Features
* Fairly fast, unintrusive, and easy to set up for simple projects
* Configuration is done in Scala
* The default source directory layout is the same as maven's so you can always switch to maven should you need/want to
* Regardless of what sources you have added, changed, or removed, sbt should (in theory) recompile the right sources using information extracted from compilation with a compiler plugin
* Supports ScalaCheck, specs, and ScalaTest.
* Can generate documentation with scaladoc
* Packages jars (classes, sources, or api docs)
* Can start the Scala interpreter with the right classpath (dependencies and compiled classes)
* Multiple project/subproject support
* Parallel task execution, including parallel test execution
* Dependency management support: basic inline declarations, configuration with Maven (partial support) or Ivy, or manual management.
Calm stands for…
Seascape Calm Weather
Seascape Calm Weather
…Calm Application Lifecycle Management, which stands for Calm Application Lifecycle Management Application Lifecycle Management … ehm just kidding ;)
Calm is an early implementation of main ALM use cases on an Open Source and collaborative framework based on Apache Maven.
What exactly is Maven Calm
Maven Calm is not just a Corporate POM. It’s a cross-corporate POM which provides lifecycle-oriented configuration for your Maven Plugins; the best way to start is having a look at the presentation! In short, your Project or Corporate POM should look like this to inherit all the ALM oriented behaviors.
Five Minute Introduction
(Note that the actual manual is located here. Also note that this plugin has not been made available through the central Maven repository yet; you should instead add http://agilejava.com/maven/ to your list of repositories.)
The Docbkx Tools project provides a number of tools for supporting DocBook in a Maven environment. This may seem odd to you, since 1) Maven 2 is supposed to support DocBook natively, relying on Doxia, and 2) there is already another DocBook plugin at mojo.codehaus.org.
The thruth however is that DocBook support in Doxia is fairly limited, mainly because Doxia as a framework supports only a small fraction of the concepts found in DocBook. The subset of DocBook supported by Doxia is not even close to simplified DocBook.
The DocBook plugin at mojo.codehaus.org is supporting a wider range of DocBook markup, and is in fact more similar to the DocBook tools provided with this project. There are however some significant differences:
* The focus is on ease of use.
* You should not be required to install additional stuff to your hard disk in order to generate content from your DocBook sources. Simply adding a reference to the plugin in your POM should be sufficient.
* This project focuses on providing dedicated support for particular DocBook XSL stylesheet distributions. That means you can rely on the dedicated parameterization mechanism of Maven Plugins to pass in the XSLT parameters defined for a particular version and type of XSLT stylesheet.
* In the DocBook Plugin found at mojo.codehaus.org, you will be required to download a specific version of the DocBook XSL stylesheets manually. The plugins packaged contain the stylesheets as well. (In this project, a particular version of the stylesheets is closely tied to a particular version of the plugin. That you means you can always rely on the plugin's documentation to know which parameters you could pass in.)
* The DocBook plugin found at mojo.codehaus.org requires you to have access to the Internet in order allow the plugin to resolve URI's. The plugins provided in this project act differently: if your DocBook sources are referening to a DTD, then you can simply add a dependency to a jar file containing the DTD and related entities, and the plugin will make sure that all references will be resolved correctly.
Impala allows you to divide a large Spring-based application into a hierarchy of modules. These modules can be dynamically added, updated or removed.
Because Impala-based applications are genuinely modular, they are much easier to maintain than vanilla Spring applications.
Impala radically boosts productivity of Spring application development. This is enabled by the dynamic module loading capability, the seamless integration with Eclipse, and the efficient mechanisms for running Spring integration tests, both individually and within suites. When writing applications you only rarely need to restart your JVM, allowing your application changes to be reflected almost instantly. No long restart waits required!
Impala also features a build system, based on ANT, and dependency management capabilities, which you can optionally use.
For up to date news on development of Impala, see the project blog.
Impala is developed under the Apache Licence, Version 2.
This article show you how you can fix bugs for maven-plugins (eclipse setup for hacking the code, debugging etc.) with a concrete project: maven-eclipse-plugin. Lets start …
Pax Construct provides a Swiss Army® knife for OSGi that helps you rapidly create, build, manage and deploy many types of OSGi bundles. The core functionality is provided by a flexible Maven2 plugin that enhances and streamlines the Maven build process for OSGi, along with intelligent archetypes that adapt according to your needs.
Unix and Windows scripts are available to further reduce the need to remember (and type) long command strings. These scripts come with basic help text and can bootstrap themselves from an empty system.
You can use Pax Construct to create a simple first bundle in less than a minute, all the way up to managing a Spring Dynamic Modules for OSGiTM system.
This plugin for Maven 2 is based on the BND tool from Peter Kriens. The way BND works is by treating your project as a big collection of classes (e.g., project code, dependencies, and the class path). The way you create a bundle with BND is to tell it the content of the bundle's JAR file as a subset of the available classes. This plugin wraps BND to make it work specifically with the Maven 2 project structure and to provide it with reasonable default behavior for Maven 2 projects.
Since the 1.4.0 release, this plugin also aims to automate OBR (OSGi Bundle Repository) management. It helps manage a local OBR for your local Maven repository, and also supports remote OBRs for bundle distribution. The plug-in automatically computes bundle capabilities and requirements, using a combination of Bindex and Maven metadata.