You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Anil Gangolli (JIRA)" <ji...@apache.org> on 2007/10/23 22:15:50 UTC
[jira] Created: (IVY-631) Retrieval not expanding "[originalname]"
Retrieval not expanding "[originalname]"
----------------------------------------
Key: IVY-631
URL: https://issues.apache.org/jira/browse/IVY-631
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-alpha-2
Environment: Ivy 2.0.0-alpha2-incubating
Ant 1.7.0
Sun JDK 1.5.0_12
Reporter: Anil Gangolli
I'm using
<ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
With the following resolver definitions:
<resolvers>
<!-- We define two resolvers and chain them to form our normal resolver.
The first is for thirdparty libraries, and the second is for libraries we build ourselves.
The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
<filesystem name="thirdparty-libs">
<ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
<!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
<artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
<artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
<artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
<!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
<artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
<artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
</filesystem>
<!-- Workaround for JIRA IVY-630 -->
<filesystem name="thirdparty-libs-no-ivy">
<!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
<artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
<artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
<artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
<!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
<artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
<artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
</filesystem>
<filesystem name="our-libs">
<ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
<!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
So we need two separate patterns. -->
<artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
<artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
<artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
<artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
</filesystem>
<chain name="localtree" returnFirst="true">
<resolver ref="thirdparty-libs"/>
<resolver ref="thirdparty-libs-no-ivy"/>
<resolver ref="our-libs"/>
</chain>
</resolvers>
The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-631) Retrieval not expanding
"[originalname]"
Posted by "Anil Gangolli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540954 ]
Anil Gangolli commented on IVY-631:
-----------------------------------
Thanks. I downloaded and built trunk. Was able to verify it now appears to work properly for my test case.
> Retrieval not expanding "[originalname]"
> ----------------------------------------
>
> Key: IVY-631
> URL: https://issues.apache.org/jira/browse/IVY-631
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Environment: Ivy 2.0.0-alpha2-incubating
> Ant 1.7.0
> Sun JDK 1.5.0_12
> Reporter: Anil Gangolli
> Assignee: Maarten Coene
> Fix For: 2.0.0-beta-1
>
> Attachments: ivytest-631.tgz
>
>
> I'm using
> <ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
> With the following resolver definitions:
> <resolvers>
> <!-- We define two resolvers and chain them to form our normal resolver.
> The first is for thirdparty libraries, and the second is for libraries we build ourselves.
> The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
> <filesystem name="thirdparty-libs">
> <ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <!-- Workaround for JIRA IVY-630 -->
> <filesystem name="thirdparty-libs-no-ivy">
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <filesystem name="our-libs">
> <ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
> <!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
> So we need two separate patterns. -->
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
> </filesystem>
> <chain name="localtree" returnFirst="true">
> <resolver ref="thirdparty-libs"/>
> <resolver ref="thirdparty-libs-no-ivy"/>
> <resolver ref="our-libs"/>
> </chain>
> </resolvers>
> The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
> This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-631) Retrieval not expanding "[originalname]"
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene resolved IVY-631.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-beta-1
It should be fixed in trunk.
Could you try it out?
> Retrieval not expanding "[originalname]"
> ----------------------------------------
>
> Key: IVY-631
> URL: https://issues.apache.org/jira/browse/IVY-631
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Environment: Ivy 2.0.0-alpha2-incubating
> Ant 1.7.0
> Sun JDK 1.5.0_12
> Reporter: Anil Gangolli
> Assignee: Maarten Coene
> Fix For: 2.0.0-beta-1
>
> Attachments: ivytest-631.tgz
>
>
> I'm using
> <ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
> With the following resolver definitions:
> <resolvers>
> <!-- We define two resolvers and chain them to form our normal resolver.
> The first is for thirdparty libraries, and the second is for libraries we build ourselves.
> The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
> <filesystem name="thirdparty-libs">
> <ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <!-- Workaround for JIRA IVY-630 -->
> <filesystem name="thirdparty-libs-no-ivy">
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <filesystem name="our-libs">
> <ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
> <!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
> So we need two separate patterns. -->
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
> </filesystem>
> <chain name="localtree" returnFirst="true">
> <resolver ref="thirdparty-libs"/>
> <resolver ref="thirdparty-libs-no-ivy"/>
> <resolver ref="our-libs"/>
> </chain>
> </resolvers>
> The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
> This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-631) Retrieval not expanding
"[originalname]"
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537579 ]
Maarten Coene commented on IVY-631:
-----------------------------------
I cannot reproduce your problem.
Could you:
- post your build.xml (or the parts where you use Ivy)
- post the output when running Ant with the -d option
Maarten
> Retrieval not expanding "[originalname]"
> ----------------------------------------
>
> Key: IVY-631
> URL: https://issues.apache.org/jira/browse/IVY-631
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Environment: Ivy 2.0.0-alpha2-incubating
> Ant 1.7.0
> Sun JDK 1.5.0_12
> Reporter: Anil Gangolli
>
> I'm using
> <ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
> With the following resolver definitions:
> <resolvers>
> <!-- We define two resolvers and chain them to form our normal resolver.
> The first is for thirdparty libraries, and the second is for libraries we build ourselves.
> The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
> <filesystem name="thirdparty-libs">
> <ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <!-- Workaround for JIRA IVY-630 -->
> <filesystem name="thirdparty-libs-no-ivy">
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <filesystem name="our-libs">
> <ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
> <!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
> So we need two separate patterns. -->
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
> </filesystem>
> <chain name="localtree" returnFirst="true">
> <resolver ref="thirdparty-libs"/>
> <resolver ref="thirdparty-libs-no-ivy"/>
> <resolver ref="our-libs"/>
> </chain>
> </resolvers>
> The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
> This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVY-631) Retrieval not expanding "[originalname]"
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene reassigned IVY-631:
---------------------------------
Assignee: Maarten Coene
> Retrieval not expanding "[originalname]"
> ----------------------------------------
>
> Key: IVY-631
> URL: https://issues.apache.org/jira/browse/IVY-631
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Environment: Ivy 2.0.0-alpha2-incubating
> Ant 1.7.0
> Sun JDK 1.5.0_12
> Reporter: Anil Gangolli
> Assignee: Maarten Coene
> Attachments: ivytest-631.tgz
>
>
> I'm using
> <ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
> With the following resolver definitions:
> <resolvers>
> <!-- We define two resolvers and chain them to form our normal resolver.
> The first is for thirdparty libraries, and the second is for libraries we build ourselves.
> The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
> <filesystem name="thirdparty-libs">
> <ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <!-- Workaround for JIRA IVY-630 -->
> <filesystem name="thirdparty-libs-no-ivy">
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <filesystem name="our-libs">
> <ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
> <!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
> So we need two separate patterns. -->
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
> </filesystem>
> <chain name="localtree" returnFirst="true">
> <resolver ref="thirdparty-libs"/>
> <resolver ref="thirdparty-libs-no-ivy"/>
> <resolver ref="our-libs"/>
> </chain>
> </resolvers>
> The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
> This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (IVY-631) Retrieval not expanding
"[originalname]"
Posted by "Anil Gangolli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538668 ]
gangolli edited comment on IVY-631 at 10/30/07 9:10 AM:
-------------------------------------------------------------
I've attached a tarball that you can use to reproduce the issue.
I used:
(1) ivytest-631.tgz (attached)
(2) apache-ivy-2.0.0-alpha2-incubating-bin-with-deps.tar.gz
(3) ant 1.7.0
(4) JDK 1.5.0_12
These commands will duplicate it are also provided in the enclosed README in the tarball. They assume you have ant in your path.
cd /tmp
tar xvfz ivytest.tgz
cd ivytest-631
tar xvfz apache-ivy-2.0.0-alpha2-incubating-bin-with-deps.tar.gz
ant
ls build/deps/compile
The name of the junit-4.1.jar will be [originalname].jar
was (Author: gangolli):
I've attached a tarball that you can use to reproduce the issue.
I used:
(1) ivytest-631.tgz (attached)
(2) apache-ivy-2.0.0-alpha2-incubating-bin-with-deps.tar.gz
(3) ant 1.7.0
(4) JDK 1.5.0_12
These commands will duplicate it are also provided in the enclosed README in the tarball. They assume you have ant in your path.
cd /tmp
tar xvfz ivytest.tgz
cd ivytest
tar xvfz apache-ivy-2.0.0-alpha2-incubating-bin-with-deps.tar.gz
ant
ls build/deps/compile
The name of the junit-4.1.jar will be [originalname].jar
> Retrieval not expanding "[originalname]"
> ----------------------------------------
>
> Key: IVY-631
> URL: https://issues.apache.org/jira/browse/IVY-631
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Environment: Ivy 2.0.0-alpha2-incubating
> Ant 1.7.0
> Sun JDK 1.5.0_12
> Reporter: Anil Gangolli
> Attachments: ivytest-631.tgz
>
>
> I'm using
> <ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
> With the following resolver definitions:
> <resolvers>
> <!-- We define two resolvers and chain them to form our normal resolver.
> The first is for thirdparty libraries, and the second is for libraries we build ourselves.
> The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
> <filesystem name="thirdparty-libs">
> <ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <!-- Workaround for JIRA IVY-630 -->
> <filesystem name="thirdparty-libs-no-ivy">
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <filesystem name="our-libs">
> <ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
> <!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
> So we need two separate patterns. -->
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
> </filesystem>
> <chain name="localtree" returnFirst="true">
> <resolver ref="thirdparty-libs"/>
> <resolver ref="thirdparty-libs-no-ivy"/>
> <resolver ref="our-libs"/>
> </chain>
> </resolvers>
> The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
> This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-631) Retrieval not expanding "[originalname]"
Posted by "Anil Gangolli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anil Gangolli updated IVY-631:
------------------------------
Attachment: ivytest-631.tgz
I've attached a tarball that you can use to reproduce the issue.
I used:
(1) ivytest-631.tgz (attached)
(2) apache-ivy-2.0.0-alpha2-incubating-bin-with-deps.tar.gz
(3) ant 1.7.0
(4) JDK 1.5.0_12
These commands will duplicate it are also provided in the enclosed README in the tarball. They assume you have ant in your path.
cd /tmp
tar xvfz ivytest.tgz
cd ivytest
tar xvfz apache-ivy-2.0.0-alpha2-incubating-bin-with-deps.tar.gz
ant
ls build/deps/compile
The name of the junit-4.1.jar will be [originalname].jar
> Retrieval not expanding "[originalname]"
> ----------------------------------------
>
> Key: IVY-631
> URL: https://issues.apache.org/jira/browse/IVY-631
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Environment: Ivy 2.0.0-alpha2-incubating
> Ant 1.7.0
> Sun JDK 1.5.0_12
> Reporter: Anil Gangolli
> Attachments: ivytest-631.tgz
>
>
> I'm using
> <ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
> With the following resolver definitions:
> <resolvers>
> <!-- We define two resolvers and chain them to form our normal resolver.
> The first is for thirdparty libraries, and the second is for libraries we build ourselves.
> The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
> <filesystem name="thirdparty-libs">
> <ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <!-- Workaround for JIRA IVY-630 -->
> <filesystem name="thirdparty-libs-no-ivy">
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <filesystem name="our-libs">
> <ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
> <!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
> So we need two separate patterns. -->
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
> </filesystem>
> <chain name="localtree" returnFirst="true">
> <resolver ref="thirdparty-libs"/>
> <resolver ref="thirdparty-libs-no-ivy"/>
> <resolver ref="our-libs"/>
> </chain>
> </resolvers>
> The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
> This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-631) Retrieval not expanding
"[originalname]"
Posted by "Anil Gangolli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538831 ]
Anil Gangolli commented on IVY-631:
-----------------------------------
Note that the test case provides a simpler case than reported. It only requires a filesystem resolver with no ivy file for the dependency.
> Retrieval not expanding "[originalname]"
> ----------------------------------------
>
> Key: IVY-631
> URL: https://issues.apache.org/jira/browse/IVY-631
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Environment: Ivy 2.0.0-alpha2-incubating
> Ant 1.7.0
> Sun JDK 1.5.0_12
> Reporter: Anil Gangolli
> Attachments: ivytest-631.tgz
>
>
> I'm using
> <ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
> With the following resolver definitions:
> <resolvers>
> <!-- We define two resolvers and chain them to form our normal resolver.
> The first is for thirdparty libraries, and the second is for libraries we build ourselves.
> The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
> <filesystem name="thirdparty-libs">
> <ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <!-- Workaround for JIRA IVY-630 -->
> <filesystem name="thirdparty-libs-no-ivy">
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <filesystem name="our-libs">
> <ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
> <!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
> So we need two separate patterns. -->
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
> </filesystem>
> <chain name="localtree" returnFirst="true">
> <resolver ref="thirdparty-libs"/>
> <resolver ref="thirdparty-libs-no-ivy"/>
> <resolver ref="our-libs"/>
> </chain>
> </resolvers>
> The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
> This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-631) Retrieval not expanding
"[originalname]"
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538928 ]
Maarten Coene commented on IVY-631:
-----------------------------------
I was able to reproduce this issue and It seems to be caused by using "latest.integration" as revision (maybe other dynamic revisions may have the same problem).
> Retrieval not expanding "[originalname]"
> ----------------------------------------
>
> Key: IVY-631
> URL: https://issues.apache.org/jira/browse/IVY-631
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-2
> Environment: Ivy 2.0.0-alpha2-incubating
> Ant 1.7.0
> Sun JDK 1.5.0_12
> Reporter: Anil Gangolli
> Attachments: ivytest-631.tgz
>
>
> I'm using
> <ivy:retrieve pattern="${deps.dir}/[conf]/[originalname].[ext]" sync="true"/>
> With the following resolver definitions:
> <resolvers>
> <!-- We define two resolvers and chain them to form our normal resolver.
> The first is for thirdparty libraries, and the second is for libraries we build ourselves.
> The chain looks first in thirdparty libraries, and then in ours. The first found is used. -->
> <filesystem name="thirdparty-libs">
> <ivy pattern="${top.dir}/thirdparty/libraries/[module](-[revision])/ivy.xml"/>
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <!-- Workaround for JIRA IVY-630 -->
> <filesystem name="thirdparty-libs-no-ivy">
> <!-- Patterns for thirdparty libs; in preferred resolution ordering. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]-[revision]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[module]/dist/[artifact].[ext]"/>
> <!-- Also supported patterns: resolution of artifacts grouped by organization and module or only organization. -->
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/[module]/dist/[artifact].[ext]"/>
> <artifact pattern="${top.dir}/thirdparty/libraries/[organisation]/dist/[artifact].[ext]"/>
> </filesystem>
> <filesystem name="our-libs">
> <ivy pattern="${top.dir}/libraries/[module]/ivy.xml"/>
> <!-- Ivy bug or lack of understanding: using optional revision (-[revision]) here doesn't work right.
> So we need two separate patterns. -->
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[organisation]-[artifact].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact]-[revision].[ext]"/>
> <artifact pattern="${top.dir}/libraries/[module]/build/dist/[artifact].[ext]"/>
> </filesystem>
> <chain name="localtree" returnFirst="true">
> <resolver ref="thirdparty-libs"/>
> <resolver ref="thirdparty-libs-no-ivy"/>
> <resolver ref="our-libs"/>
> </chain>
> </resolvers>
> The behavior I am seeing is that whenever the artifact is resolved using the last resolver in this chain (the resolver named "our-libs" above) the artifact gets retrieved to the proper directory but with the name (verbatim) "[originalname].jar", rather than the name with the appropriate value of "[originalname]" substituted in.
> This happens in 2.0.0-alpha2-incubating but was not occurring in 1.4.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.