maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Black (JIRA)" <>
Subject [jira] Commented: (MCOMPILER-67) NullPointerException when compiling with maven-compiler-plugin 2.1-SNAPSHOT - all projects
Date Wed, 13 Feb 2008 18:32:29 GMT


Jeff Black commented on MCOMPILER-67:

The workaround (or permanent solution, I'm not sure yet) is to define the compiler plugin
in your pom with an explicit version, <version>2.0.2</version>.

Surely there has to be a better way to say "For all the standard plugins that I use and do
not specify a version for, please use the latest release version, and never a SNAPSHOT version".
 Defining all the plugin versions, even in a single parent pom, seems unreasonable to me.
 Why would the default be to use plugin SNAPSHOTS?  Doesn't this create a fragile project

What is the best practice way to have a rock solid project, isolated from deployed SNAPSHOT

> NullPointerException when compiling with maven-compiler-plugin 2.1-SNAPSHOT - all projects
> ------------------------------------------------------------------------------------------
>                 Key: MCOMPILER-67
>                 URL:
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: WinXP, Java 1.5
>            Reporter: Mike Rokitka
>         Attachments: outfile.txt
> All of my compiles using Maven have failed, and they were previously working fine yesterday.
 I believe it is likely due to a bug in the snapshot.  I've tried using different versions
of the Java, and upgraded to Maven 2.0.8 from 2.0.7, but that had no effect.
> Attached is the full trace with debug enabled.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message