[jira] Reopened: (MNG-115) versions of managed dependencies attached to transdeps are not resolved correctly

["Andrew Williams (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Williams reopened MNG-115:
---------------------------------


This appears to still be problematic on trunk, but only when running surefire tests.
perhaps someone can comment on this? there was a lot of "flux" with surefire recently.


> versions of managed dependencies attached to transdeps are not resolved correctly
> ---------------------------------------------------------------------------------
>
>                 Key: MNG-115
>                 URL: http://jira.codehaus.org/browse/MNG-115
>             Project: Maven 2
>          Issue Type: Bug
>         Environment: all
>            Reporter: John Casey
>         Assigned To: John Casey
>            Priority: Critical
>             Fix For: 2.0-alpha-1
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> When resolving dependencies transitively, each dependency's POM is retrieved, read, and parsed for its dependencies, and the cycle continues. Since we're dealing with Model's here, and not MavenProject's, dependency management has not taken place. This means the managed dependencies in that model will have a version (and other info, potentially) which is null. This leads to a NPE in the transdeps resolution process.
> Proposal: Switch transitive resolution to use MavenProject rather than Model, which will alleviate any problems with post-processing and inheritance calculations on the Model. This will make inclusion of parent POM's easier too, along with resolution of interpolated values within the POM.

-- 
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