[
https://issues.apache.org/jira/browse/IVY-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Bonanno updated IVY-616:
----------------------------
Attachment: patch.txt
I wanted to re-base the patch for this issue on the latest code. Unfortunately
I have hit a snag.
The current implementation needs to be able to read the parent POMs and look
for the dependency management element. The parent POMs were parsed using the
same resolver that is parsing the current POM.
The implementation used the resolver that was available through IvyContext's
stack. The resolver was pushed by the BasisResolver. However,
IvyContext.getResolver is no longer available because of issue 610.
I have attached the patch converted to the latest code, I have an
implementation that works on alpha 2. But I need to figure out a workaround to
obtaining the current resolver. If someone has a suggestion that would be great.
Thanks
Jim
> Maven Dependency Management is not used to determine artifact version
> ---------------------------------------------------------------------
>
> Key: IVY-616
> URL: https://issues.apache.org/jira/browse/IVY-616
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.0-alpha-2
> Reporter: Jim Bonanno
> Fix For: 2.0.0-beta-1
>
> Attachments: patch.txt
>
>
> We recently hit an issue with resolving some POMs with the ibiblio resolver
> and usepoms=true. The problem is that the version for a dependency can be
> stored in the dependency management section of a parent POM.
> The apache directory server is an example.
> http://repo1.maven.org/maven2/org/apache/directory/server/apacheds-server-main/1.5.0/apacheds-server-main-1.5.0.pom
> Note that the POM for the parent build artifact has the version information
> for the last 5 dependencies.
> The PomModuleDescriptorParser currently only builds a dependency descriptor
> if the groupId, artifactId and version are all set. So for the case of apache
> directory server, many of the transitive dependencies are ignored.
> I have been working on an extension to the PomModuleDescriptorParser that
> build the dependency management information at the end of the project/parent
> element by parsing the parent chain. Then if a dependency is found without a
> version, then the dependency management information is used. I attach the
> patch after some more testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
