You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2008/05/22 01:03:56 UTC
[jira] Commented: (IVY-811) Maven scope defined in POM
dependencyManagement section not honoured
[ https://issues.apache.org/jira/browse/IVY-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598846#action_12598846 ]
Maarten Coene commented on IVY-811:
-----------------------------------
I've committed a fix for this problem to SVN trunk. Could you give it a try?
I'm leaving this issue open untill I have found the time to add a junit test.
> Maven scope defined in POM dependencyManagement section not honoured
> --------------------------------------------------------------------
>
> Key: IVY-811
> URL: https://issues.apache.org/jira/browse/IVY-811
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.0.0-beta-2
> Environment: * Windows XP SP2
> * Sun Java 6 SE 1.6.0_05
> * Apache Ant 1.7.0
> Reporter: Rick Riemer
> Assignee: Maarten Coene
> Fix For: 2.0-RC1
>
> Attachments: ivy-1.2-picocontainer.xml, ivy-1.2_picocontainer-parent.xml, picocontainer-parent.original-1.2.pom, picocontainer.original-1.2.pom
>
>
> When resolving dependencies from Maven POMs, Ivy seems to ignore the dependency scopes as defined in the dependencyManagement section. For example when our project imports the org.picocontainer#picocontainer;1.2 project, Ivy considers xpp3#xpp3 and xstream#xstream as normal dependencies, while picocontainer-parent only includes them on test scope.
> I will attach the picocontainer POMs and the generated Ivy file to show what happens.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.