15
2009
Maven Tip: Enforcing a JDK version in your build
You’ve just got to love the Maven Enforcer plugin. Anything with a byline of “The Loving Iron Fist of Maven” has got to endear you, no?
The Enforcer is a collection of configurable rules that will force your build to stop if certain preconditions are not met. One of the common ways I’ve been using it lately is to ensure that a certain JDK (1.4 in my case – don’t get me started on Websphere) is used when producing production artifacts.
I know what you’re thinking, just use the <target> config attribute to the compiler plugin? That would be true if the -target switches to the JDK compiler actually did what you think. But alas that is not the case unless you do funkiness with paths to the 1.4 runtime with a -bootclasspath option which sounds just too fragile and machine-specific. I’d prefer to just bomb out early if it’s not a real 1.4 JDK. I’m really dislike that java.lang.NoSuchMethodError stuff.
Anyways, here’s the build kungfu to ensure you enforce your preferred JDK:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <version>1.0-beta-1</version> <executions> <execution> <id>enforce-versions</id> <phase>validate</phase> <goals> <goal>enforce</goal> </goals> <configuration> <rules> <requireJavaVersion> <version>[1.4,1.5)</version> </requireJavaVersion> </rules> </configuration> </execution> </executions> </plugin>
Putting the goal against the validate phase makes everything die early. However, you might want to bind to "install" or whatever if you're happy to develop against a later JDK. Giving this bad boy a run on Snow Leopard will give you output like:
[INFO] [enforcer:enforce {execution: enforce-versions}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion
failed with message:
Detected JDK Version: 1.6.0-15 is not in the allowed range [1.4,1.5).
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
Giddy up. Die early, die often.
I’m definitely making room for the Enforcer plugin in my Maven Quickstart Course running in Canberra next month. It’s gonna be a blast – and there’s still early bird pricing for the next week so if you’re interested in getting there, don’t forget to register early!
Enjoy the loving iron fist!
2 Comments + Add Comment
Leave a comment
Glen Smith
Archives
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- January 2011
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003

An article by Glen





Hi Glen,
it is much easier to achieve the same effect (and more) using other tools, e.g. Gradle. See here: http://kaczanowscy.pl/tomek/2009-07/ant-gradle-and-maven-comparison-checking-build-prerequisites
–
best regards
Tomek Kaczanowski
How about when you have a Maven project where different modules needs to be built with different JDK versions?
I guess the Enforcer plugin would stop you from building with the wrong JDK version but that will not help you when you want to build the whole project.