yes it did:
http://jira.codehaus.org/browse/MNG-565
was the ticket and patch.
--
Kris Bravo
Corridor Software, Inc.
http://www.corridor-software.us
> [ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42735 ]
>
> John Casey commented on MNG-556:
> --
[ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42735 ]
John Casey commented on MNG-556:
I thought I saw a fix for this go flying by in the commit emails. I'll verify
and fix if it hasn't already been done.
> NPE in MavenProject class
> -
*checks pockets*
Not yet. Finishing up the xmlbeans plugin right now. But I'll add one to
the ticket later today.
In the mean time, what should I look for to determine if the
@requiresDependencyResolution tag is present? I want to be certain the
exception is only thrown if it isn't set and not whe
[ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42572 ]
Emmanuel Venisse commented on MNG-556:
--
do you have a patch?
> NPE in MavenProject class
> -
>
> Key: MNG-556
> URL: http://jira.codehaus.or
[ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42571 ]
Trygve Laugstol commented on MNG-556:
-
Throwing a exception instead of silently ignoring it is definitely a better
solution.
> NPE in MavenProject class
> -
>
[ http://jira.codehaus.org/browse/MNG-556?page=comments#action_42570 ]
Corridor Software Developer commented on MNG-556:
-
Ran into this as well while developing a plugin, only it was caused by not
having @requiresDependencyResolution in the
