You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2010/10/21 18:20:16 UTC
[jira] Created: (IVY-1240) Only the last dependency descriptor is
taken into account on the same module
Only the last dependency descriptor is taken into account on the same module
----------------------------------------------------------------------------
Key: IVY-1240
URL: https://issues.apache.org/jira/browse/IVY-1240
Project: Ivy
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Nicolas Lalevée
In some of our project we had:
{code:xml}
<dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf1" />
<dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf2" />
<dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf3" />
{code}
When resolving dependencies with the conf "*", the resulting "compile" conf report did contain dependencies of the conf1, conf2 and conf3 of mymodule. But the resulting "runtime" conf report, contained only the configuration of conf3 of mymodule.
Changing the dependency into the following one fixed it:
{code:xml}
<dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf1,conf2,conf3" />
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-1240) Only the last dependency descriptor is
taken into account on the same module
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923509#action_12923509 ]
Nicolas Lalevée commented on IVY-1240:
--------------------------------------
I did try to make a unit test, but I was not able to reproduce the issue. I think I have found the culprit though by debugging while resolving on my project.
So I will commit the fix and the unit test, even if the unit test didn't actually fail before the apply of the fix.
> Only the last dependency descriptor is taken into account on the same module
> ----------------------------------------------------------------------------
>
> Key: IVY-1240
> URL: https://issues.apache.org/jira/browse/IVY-1240
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Nicolas Lalevée
>
> In some of our project we had:
> {code:xml}
> <dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf1" />
> <dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf2" />
> <dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf3" />
> {code}
> When resolving dependencies with the conf "*", the resulting "compile" conf report did contain dependencies of the conf1, conf2 and conf3 of mymodule. But the resulting "runtime" conf report, contained only the configuration of conf3 of mymodule.
> Changing the dependency into the following one fixed it:
> {code:xml}
> <dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf1,conf2,conf3" />
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-1240) Only the last dependency descriptor is
taken into account on the same module
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Lalevée resolved IVY-1240.
----------------------------------
Resolution: Fixed
Fix Version/s: trunk
Assignee: Nicolas Lalevée
> Only the last dependency descriptor is taken into account on the same module
> ----------------------------------------------------------------------------
>
> Key: IVY-1240
> URL: https://issues.apache.org/jira/browse/IVY-1240
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Nicolas Lalevée
> Assignee: Nicolas Lalevée
> Fix For: trunk
>
>
> In some of our project we had:
> {code:xml}
> <dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf1" />
> <dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf2" />
> <dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf3" />
> {code}
> When resolving dependencies with the conf "*", the resulting "compile" conf report did contain dependencies of the conf1, conf2 and conf3 of mymodule. But the resulting "runtime" conf report, contained only the configuration of conf3 of mymodule.
> Changing the dependency into the following one fixed it:
> {code:xml}
> <dependency org="org" name="mymodule" rev="1.0" conf="compile,runtime->conf1,conf2,conf3" />
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.