You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Patrick Woodworth (JIRA)" <ji...@apache.org> on 2008/10/20 14:25:44 UTC
[jira] Created: (IVY-951) Correctly set ivy.resolved.configurations
property when the conf string includes a negation operator.
Correctly set ivy.resolved.configurations property when the conf string includes a negation operator.
-----------------------------------------------------------------------------------------------------
Key: IVY-951
URL: https://issues.apache.org/jira/browse/IVY-951
Project: Ivy
Issue Type: Bug
Components: Ant
Affects Versions: 2.0-RC1
Reporter: Patrick Woodworth
Really this is a continuation of the work begun in [IVY-894|https://issues.apache.org/jira/browse/IVY-894]. The previous work allowed the resolve task to handle a configuration list with negation operators, by transforming the list during the wildcard fixup. Unfortunately however, in this type of scenario the ivy.resolved.configurations property is still set to the original string with negation operators intact. This situation breaks postresolve tasks (e.g. retrieve) that simply reuse the value of the ivy.resolved.configurations property when it's not explicitly passed to the subsequent postresolve task. The new patch attached to this bug report fixes the issue by appropriately setting the ivy.resolved.configurations with the post-fixup list of configurations. The patch includes an update to the testcase as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-951) Correctly set
ivy.resolved.configurations property when the conf string includes a
negation operator.
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene resolved IVY-951.
-------------------------------
Resolution: Fixed
Fix Version/s: trunk
Thank you for your contribution!
I've applied your patch into SVN trunk.
> Correctly set ivy.resolved.configurations property when the conf string includes a negation operator.
> -----------------------------------------------------------------------------------------------------
>
> Key: IVY-951
> URL: https://issues.apache.org/jira/browse/IVY-951
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0-RC1
> Reporter: Patrick Woodworth
> Assignee: Maarten Coene
> Fix For: trunk
>
> Attachments: IVY-951.patch
>
>
> Really this is a continuation of the work begun in IVY-894. The previous work allowed the resolve task to handle a configuration list with negation operators, by transforming the list during the wildcard fixup. Unfortunately however, in this type of scenario the ivy.resolved.configurations property is still set to the original string with negation operators intact. This situation breaks postresolve tasks (e.g. retrieve) that simply reuse the value of the ivy.resolved.configurations property when it's not explicitly passed to the subsequent postresolve task. The new patch attached to this bug report fixes the issue by appropriately setting the ivy.resolved.configurations with the post-fixup list of configurations. The patch includes an update to the testcase as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-951) Correctly set ivy.resolved.configurations
property when the conf string includes a negation operator.
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-951:
------------------------------
Fix Version/s: (was: trunk)
2.0-RC2
> Correctly set ivy.resolved.configurations property when the conf string includes a negation operator.
> -----------------------------------------------------------------------------------------------------
>
> Key: IVY-951
> URL: https://issues.apache.org/jira/browse/IVY-951
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0-RC1
> Reporter: Patrick Woodworth
> Assignee: Maarten Coene
> Fix For: 2.0-RC2
>
> Attachments: IVY-951.patch
>
>
> Really this is a continuation of the work begun in IVY-894. The previous work allowed the resolve task to handle a configuration list with negation operators, by transforming the list during the wildcard fixup. Unfortunately however, in this type of scenario the ivy.resolved.configurations property is still set to the original string with negation operators intact. This situation breaks postresolve tasks (e.g. retrieve) that simply reuse the value of the ivy.resolved.configurations property when it's not explicitly passed to the subsequent postresolve task. The new patch attached to this bug report fixes the issue by appropriately setting the ivy.resolved.configurations with the post-fixup list of configurations. The patch includes an update to the testcase as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-951) Correctly set ivy.resolved.configurations
property when the conf string includes a negation operator.
Posted by "Patrick Woodworth (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Woodworth updated IVY-951:
----------------------------------
Attachment: IVY-951.patch
Fix with updated testcase included.
> Correctly set ivy.resolved.configurations property when the conf string includes a negation operator.
> -----------------------------------------------------------------------------------------------------
>
> Key: IVY-951
> URL: https://issues.apache.org/jira/browse/IVY-951
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0-RC1
> Reporter: Patrick Woodworth
> Attachments: IVY-951.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> Really this is a continuation of the work begun in [IVY-894|https://issues.apache.org/jira/browse/IVY-894]. The previous work allowed the resolve task to handle a configuration list with negation operators, by transforming the list during the wildcard fixup. Unfortunately however, in this type of scenario the ivy.resolved.configurations property is still set to the original string with negation operators intact. This situation breaks postresolve tasks (e.g. retrieve) that simply reuse the value of the ivy.resolved.configurations property when it's not explicitly passed to the subsequent postresolve task. The new patch attached to this bug report fixes the issue by appropriately setting the ivy.resolved.configurations with the post-fixup list of configurations. The patch includes an update to the testcase as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-951) Correctly set ivy.resolved.configurations
property when the conf string includes a negation operator.
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-951:
------------------------------
Description: Really this is a continuation of the work begun in IVY-894. The previous work allowed the resolve task to handle a configuration list with negation operators, by transforming the list during the wildcard fixup. Unfortunately however, in this type of scenario the ivy.resolved.configurations property is still set to the original string with negation operators intact. This situation breaks postresolve tasks (e.g. retrieve) that simply reuse the value of the ivy.resolved.configurations property when it's not explicitly passed to the subsequent postresolve task. The new patch attached to this bug report fixes the issue by appropriately setting the ivy.resolved.configurations with the post-fixup list of configurations. The patch includes an update to the testcase as well. (was: Really this is a continuation of the work begun in [IVY-894|https://issues.apache.org/jira/browse/IVY-894]. The previous work allowed the resolve task to handle a configuration list with negation operators, by transforming the list during the wildcard fixup. Unfortunately however, in this type of scenario the ivy.resolved.configurations property is still set to the original string with negation operators intact. This situation breaks postresolve tasks (e.g. retrieve) that simply reuse the value of the ivy.resolved.configurations property when it's not explicitly passed to the subsequent postresolve task. The new patch attached to this bug report fixes the issue by appropriately setting the ivy.resolved.configurations with the post-fixup list of configurations. The patch includes an update to the testcase as well.)
Assignee: Maarten Coene
Remaining Estimate: (was: 0.5h)
Original Estimate: (was: 0.5h)
> Correctly set ivy.resolved.configurations property when the conf string includes a negation operator.
> -----------------------------------------------------------------------------------------------------
>
> Key: IVY-951
> URL: https://issues.apache.org/jira/browse/IVY-951
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.0-RC1
> Reporter: Patrick Woodworth
> Assignee: Maarten Coene
> Attachments: IVY-951.patch
>
>
> Really this is a continuation of the work begun in IVY-894. The previous work allowed the resolve task to handle a configuration list with negation operators, by transforming the list during the wildcard fixup. Unfortunately however, in this type of scenario the ivy.resolved.configurations property is still set to the original string with negation operators intact. This situation breaks postresolve tasks (e.g. retrieve) that simply reuse the value of the ivy.resolved.configurations property when it's not explicitly passed to the subsequent postresolve task. The new patch attached to this bug report fixes the issue by appropriately setting the ivy.resolved.configurations with the post-fixup list of configurations. The patch includes an update to the testcase as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.