You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jesse McConnell (JIRA)" <ji...@codehaus.org> on 2005/08/22 20:26:02 UTC
[jira] Created: (MNG-772) maven-eclipse-plugin NPE during writing setting file.
maven-eclipse-plugin NPE during writing setting file.
-----------------------------------------------------
Key: MNG-772
URL: http://jira.codehaus.org/browse/MNG-772
Project: Maven 2
Type: Bug
Reporter: Jesse McConnell
Attachments: eclipse-plugin.patch
the maven eclipse plugin was certain that if the maven-compiler-plugin was mentioned in the artifacts list that it would have source and target values defined.
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<encoding>iso-8859-1</encoding>
</configuration>
</plugin>
I don't and the eclipse plugin was blowing up with a NPE for this.
I patched it to check for the child Xpp3Dom objects to actually exist before trying to get their values, which was the cause of the NPE.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-772) maven-eclipse-plugin NPE during writing setting file.
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-772?page=all ]
Kenney Westerhof closed MNG-772:
--------------------------------
Resolution: Fixed
Fix Version: 2.0-beta-1
Applied your patch (with modifications). Thanks!
(I assumed the merged mojo config would specify the defaults for source/target. Assumption is the mother of all
screwups). :-)
> maven-eclipse-plugin NPE during writing setting file.
> -----------------------------------------------------
>
> Key: MNG-772
> URL: http://jira.codehaus.org/browse/MNG-772
> Project: Maven 2
> Type: Bug
> Reporter: Jesse McConnell
> Assignee: Kenney Westerhof
> Fix For: 2.0-beta-1
> Attachments: eclipse-plugin.patch
>
>
> the maven eclipse plugin was certain that if the maven-compiler-plugin was mentioned in the artifacts list that it would have source and target values defined.
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <encoding>iso-8859-1</encoding>
> </configuration>
> </plugin>
> I don't and the eclipse plugin was blowing up with a NPE for this.
> I patched it to check for the child Xpp3Dom objects to actually exist before trying to get their values, which was the cause of the NPE.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org