You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/02/04 04:39:14 UTC
[jira] Created: (MNG-115) versions of managed dependencies attached to transdeps are not resolved correctly
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-115
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-115
Summary: versions of managed dependencies attached to transdeps are not resolved correctly
Type: Bug
Status: Unassigned
Priority: Critical
Original Estimate: 3 hours
Time Spent: Unknown
Remaining: 3 hours
Project: m2
Fix Fors:
1.0-alpha-1
Assignee:
Reporter: John Casey
Created: Thu, 3 Feb 2005 10:38 PM
Updated: Thu, 3 Feb 2005 10:38 PM
Environment: all
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (MNG-115) versions of managed dependencies attached to transdeps are not resolved correctly
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-115
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-115
Summary: versions of managed dependencies attached to transdeps are not resolved correctly
Type: Bug
Status: Closed
Priority: Critical
Resolution: FIXED
Original Estimate: 3 hours
Time Spent: Unknown
Remaining: 3 hours
Project: m2
Fix Fors:
1.0-alpha-1
Assignee: John Casey
Reporter: John Casey
Created: Thu, 3 Feb 2005 10:38 PM
Updated: Thu, 3 Feb 2005 11:07 PM
Environment: all
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (MNG-115) versions of managed dependencies attached to transdeps are not resolved correctly
Posted by ji...@codehaus.org.
Message:
The following issue has been resolved as FIXED.
Resolver: John Casey
Date: Thu, 3 Feb 2005 11:06 PM
alright, so it didn't take 3 hours...
replaced Model/MavenXpp3Reader with MavenProjectBuilder in MavenMetadataSource, to incorporate all post-processing and inheritance calculations in a model before using it to transitively retrieve artifacts.
I've tested this in marmalade/marmalade-taglibs/jelly-core. I'm not sure the maven-core-it-verifier will allow me to conduct one integration test with 2-3 POM's, so I'm unsure how best to setup an integration test for this.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MNG-115
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MNG-115
Summary: versions of managed dependencies attached to transdeps are not resolved correctly
Type: Bug
Status: Resolved
Priority: Critical
Resolution: FIXED
Original Estimate: 3 hours
Time Spent: Unknown
Remaining: 3 hours
Project: m2
Fix Fors:
1.0-alpha-1
Assignee: John Casey
Reporter: John Casey
Created: Thu, 3 Feb 2005 10:38 PM
Updated: Thu, 3 Feb 2005 11:06 PM
Environment: all
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira