[
http://jira.codehaus.org/browse/MCOMPILER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123653
]
Mike Rokitka commented on MCOMPILER-67:
---------------------------------------
Thanks a lot for the info Jeff.
I suppose we can make use of the enforcer plugin to force non-snapshot versions
be used. Manually defining all the versions is kind of tedious and annoying
though.
Perhaps a better mechanism can be implemented that will allow for non-SNAPSHOT
plugins from being used as the default.
Something like what is mentioned here:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
> NullPointerException when compiling with maven-compiler-plugin 2.1-SNAPSHOT -
> all projects
> ------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-67
> URL: http://jira.codehaus.org/browse/MCOMPILER-67
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
