You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mike Rokitka (JIRA)" <ji...@codehaus.org> on 2008/02/13 16:36:28 UTC
[jira] Created: (MCOMPILER-67) NullPointerException when compiling
with maven-compiler-plugin 2.1-SNAPSHOT - all projects
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
[jira] Commented: (MCOMPILER-67) NullPointerException when
compiling with maven-compiler-plugin 2.1-SNAPSHOT - all projects
Posted by "Mike Rokitka (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MCOMPILER-67) NullPointerException when compiling
with maven-compiler-plugin 2.1-SNAPSHOT - all projects
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MCOMPILER-67.
---------------------------------
Resolution: Fixed
It's fixed now.
> 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
[jira] Commented: (MCOMPILER-67) NullPointerException when
compiling with maven-compiler-plugin 2.1-SNAPSHOT - all projects
Posted by "Jeff Black (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123564 ]
Jeff Black commented on MCOMPILER-67:
-------------------------------------
The latest thinking seems to be captured here: http://docs.codehaus.org/display/MAVEN/Plugin+packs+and+concrete+versioning
> 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
[jira] Commented: (MCOMPILER-67) NullPointerException when
compiling with maven-compiler-plugin 2.1-SNAPSHOT - all projects
Posted by "Jeff Black (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123563 ]
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 structure?
What is the best practice way to have a rock solid project, isolated from deployed SNAPSHOT plugins?
> 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
[jira] Commented: (MCOMPILER-67) NullPointerException when
compiling with maven-compiler-plugin 2.1-SNAPSHOT - all projects
Posted by "Jerrold Eads (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123663 ]
Jerrold Eads commented on MCOMPILER-67:
---------------------------------------
Gentlemen,
All of the ideas expressed in the comments are valid but how does this type of anomally occur? Isn't the update for the compiler being tested prior to checkin?
The codehaus repository doesn't have a version 1.6-SNAPSHOT for the plexus-compiler-api? Is this going to be dealt with or should everyone apply one of the solutions provided? As a Maven user this is disturbing since my whole team was not able to compile after the change.
Thanks
Jerry
> 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