Maven 2.x Tips

If you have a Maven 2.x tip, send it to us and we'll post it.

M2 Tip #3: Debugging a Maven2 pom.xml

When you have several layers of inheritance, including different settings.xml and such it is really hard to find out what's wrong. Fortunately there's a way to see your pom.xml as it is resolved by Maven2! … continue

General tip: Finding the version of a JAR

when you're converting an existing Ant project to Maven, one of the first tedious task is to find out the version of the jars that you had been using. Of course you can try to open the JAR and look for the Manifest file but alas in most cases the version is not filled… … continue

General tip: Depending on J2EE

If you're building a J2EE application you'll need to add a dependency on the J2EE JAR in your POM. You have probably noticed that the Sun J2EE JAR is not available on ibiblio. This is due to licensing restrictions. … continue

M2 Tip#2: Using Pojo to configure Mojo

It is possible to use Plain Old Java Objects (POJOs) to configure a maven 2 plugin. POJOs of different types could even be used, provided they share the same base class or interface. Note that your POJOs need to be located in the same package as the Mojo to configure and should have a default public constructor. … continue

M2 Tip#1: Passing any XML to Mojos

It is possible to pass an arbitrary XML configuration snippet to a m2 mojo by using the following: … continue