SoftwareEntwicklung Beratung Schulung

A coders, hackers heaven.....Hm...I do not think so...

Apache Maven Fludio Skin Version 1.4 Released

| Comments

The Apache Maven team is pleased to announce the release of the Apache Maven Fluido Skin Version 1.4.

The Apache Maven Fluido Skin is an Apache Maven site skin built on top of Twitter’s Bootstrap 2.3.2.

Please be aware of the new location of our issue tracker which has been moved from Codehaus to Apache Software Foundation

1
2
3
4
5
<skin>
  <groupId>org.apache.maven.skins</groupId>
  <artifactId>maven-fluido-skin</artifactId>
  <version>1.4</version>
</skin>

Apache Maven Version 3.3.3 Released

| Comments

The new Maven 3.3.3 Release is out.

Bugs:

  • MNG-5605 – ssh-wagon hangs
  • MNG-5793 – same class realm registered both with plugin and extensions realm caches
  • MNG-5795 – Maven extensions can not be retrieved from authenticated repositories
  • MNG-5797 – ‘mvn deploy’ sends HTTP User-Agent twice

Improvements:

  • MNG-5794 – Warn about Proxies with duplicate id, but different protocols
  • MNG-5808 – Upgrade Maven to use Wagon 2.9

  • The Apache Maven Team.

Apache Maven Assembly Plugin Version 2.5.4 Released

| Comments

The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.4.

The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single distributable archive.

This release is mostly a bugfix release, but due to MASSEMBLY-764 we also gained multithreaded ZIP compression, which should especially benefit users with large zip files.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-assembly-plugin</artifactId>
  <version>2.5.4</version>
</plugin>

Apache Maven Release Plugin Version 2.5.2 Released

| Comments

The Apache Maven team is pleased to announce the release of the Apache Maven Release Plugin, version 2.5.2.

This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>2.5.2</version>
</plugin>

Apache Maven Verifier Plugin Version 1.1 Released

| Comments

The Apache Maven team is pleased to announce the release of the Apache Maven Verifier Plugin, version 1.1.

Useful for integration tests – verifies the existence of certain conditions.

Please be aware of the new location of our issue tracker which has been moved from Codehaus to Apache Software Foundation.

1
2
3
4
5
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-verifier-plugin</artifactId>
  <version>1.1</version>
</plugin>

Apache Maven JavaDoc Plugin Version 2.10.3 Released

| Comments

The Apache Maven team is pleased to announce the release of the Apache Maven JavaDoc Plugin, version 2.10.3.

The Javadoc Plugin uses the Javadoc tool to generate javadocs for the specified project.

Please be aware of the new location of our issue tracker which has been moved from Codehaus to Apache Software Foundation.

1
2
3
4
5
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-javadoc-plugin</artifactId>
  <version>2.10.3</version>
</plugin>

Apache Maven DOCCK Plugin Version 1.1 Released

| Comments

The Apache Maven team is pleased to announce the release of the Apache Maven DOCCK, version 1.1.

This plugin checks that a project complies with the Plugin Documentation Standard.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-docck-plugin</artifactId>
  <version>1.1</version>
</plugin>

Please be aware of the new location of our issue tracker. which has been moved from Codehaus to Apache Software Foundation

Maven Prerequisites?

| Comments

Starting with Maven 3.3.1 it is possible to define several important configuration elements within your project. For example JVM parameters or some kind of build extensions. Unfortunately using such things may result is wrong or failing builds cause thos informations are not read by older Maven versions. How can you prevent such situations?

For a long time the prerequisites exists which defines the minimum Maven version to build with. I have to emphasize the build time.

One thing would be to define a prerequisites for your project which uses the new Maven 3.3.1 features like this in your pom.xml:

1
2
3
4
5
6
7
8
9
10
<project xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
                      http://maven.apache.org/xsd/maven-4.0.0.xsd">
  ...
  <prerequisites>
    <maven>3.3.1</maven>
  </prerequisites>
  ...
</project>

The problem with prerequisites is that it had been marked deprecated for a long time (starting with Maven 3.0 MNG-4840, MNG-5297, MNG-5501) and the intention of prerequisites was to prevent maven plugins running with the wrong Maven versions. I supose you are not writing a plugin but you would like to prevent people from trying to build your project with the wrong Maven version which might fail or produces weird results. So the real questions comes up. What to do?

The simple solution for this problem is the maven-enforcer-plugin. By using the following in your pom file:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
<build>
  <plugins>
    ...
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-enforcer-plugin</artifactId>
      <version>1.4</version>
      <executions>
        <execution>
          <id>enforce-maven</id>
          <goals>
            <goal>enforce</goal>
          </goals>
          <configuration>
            <rules>
              <requireMavenVersion>
                <version>3.3.1</version>
              </requireMavenVersion>
            </rules>
          </configuration>
        </execution>
      </executions>
    </plugin>
    ...
  </plugins>
</build>

you will prevent anyone from using an earlier version of Maven than 3.3.1. This solutions will also prevent Maven 2.2.1 from trying to start building such a project.

A best practice is to define such enforcer rule into the company parent pom to define the minimum Maven versions you would like to support with your builds.

The conclusion is to use the maven-enforcer-plugin rule only to define the minimum maven version to build with.

Apache Maven Invoker Plugin Version 1.10 Released

| Comments

The Apache Maven team is pleased to announce the release of the Apache Maven Invoker Plugin, version 1.10.

The Invoker Plugin is used to run a set of Maven projects. The plugin can determine whether each project execution is successful, and optionally can verify the output generated from a given project execution.

This plugin is in particular handy to perform integration tests for other Maven plugins. The Invoker Plugin can be employed to run a set of test projects that have been designed to assert certain features of the plugin under test.

You should specify the version in your project’s plugin configuration:

1
2
3
4
5
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-invoker-plugin</artifactId>
  <version>1.10</version>
</plugin>