[ http://jira.codehaus.org/browse/MNG-781?page=comments#action_45148 ]
Kenney Westerhof commented on MNG-781: -------------------------------------- The problem is indeed that the plugin configuration is null when the configuration is specified in an <execution> element. When it's specified as a child to <plugin>, or when it's totally absent, it is not null (i.e. either the defined config or the plugin.xml's configuration is present.). It seems to me a plugin's config should not be reset to null (but the default in the plugin.xml kept) when a config is specified in the <execution>. Btw, binding to a phase or not does not have any effect. > NPE in maven-eclipse-plugin when binds maven-compiler-plugin in initialize > phase > -------------------------------------------------------------------------------- > > Key: MNG-781 > URL: http://jira.codehaus.org/browse/MNG-781 > Project: Maven 2 > Type: Bug > Components: maven-plugins > Versions: 2.0-beta-1 > Environment: xp > Reporter: Dan Tran > Fix For: 2.0-beta-1 > Attachments: pom.xml, stacktrace.txt > > > When I bind maven-compiler-plugin in initialize phase, eclispe plugin throws > NPE. > When I remove the binding. It is ok > Note in pom.xml, I compile all of other plugins except the compiler plugin. > the NPE was thru because plugin.configuration return null -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
