ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Per Hermansson (JIRA)" <>
Subject [jira] Commented: (IVY-779) resolve fails to put metadata in cache
Date Fri, 04 Apr 2008 12:47:26 GMT


Per Hermansson commented on IVY-779:

Sorry for the delay. 
Good new is that when using Ivy from the latest trunk (rev: 644689) the ant task finishes
without error.

But Ivy no longer behaves as expected: 
In the ant build file, attached to this issue, I first resolve module A and then retrieves
all dependencies to the output folder.
After the task has executed only the module B (A depends on B) is copied to the destination
folder, not module A.

The issue seems to be that the artifacts for the module described by the "input" Ivy file
isn't resolved.

> resolve fails to put metadata in cache
> --------------------------------------
>                 Key: IVY-779
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-beta-1, 2.0.0-beta-2
>         Environment: Windows XP, Java 1.6, Ant 1.7
> Ubuntu, Java 1.5, Ant 1.6.5
>            Reporter: Per Hermansson
>            Assignee: Maarten Coene
>             Fix For: 2.0-RC1
>         Attachments: debug-beta1.log, debug-beta2.log, output-beta1.log, output-beta2.log,
> Ivy fails to put module metadata in cache resulting in incomplete artifact retrieving.
> I've created a sample project containing two modules, a and b. Module a depends on b
(both modules has a single artifact a.jar and b.jar).
> With the following ant build file:
> 	<target name="test">
> 		<ivy:cleancache />
> 		<ivy:resolve file="repository/a/ivy.xml" />
> 		<ivy:retrieve ivypattern="output/[module]/[artifact].[ext]" pattern="output/[module]/[artifact].[ext]"
> 	</target>
> The following happens using Ivy 2.0.0-beta2:
> Ivy gives a warning that it failed to put ivy.xml for module b in cache.
> Later during the retrieve step only the artifact b.jar is copied to the destination folder
and not any of the following: a.jar nor the ivy files for module a and b.
> When using Ivy 2.0.0-beta1:
> The resolve step gives the same warning.
> Then the build fails during the retrieve step because Ivy can't find the ivy.xml file
for module b in the cache.
> This is probably another bug (or a feature?) since Ivy isn't failing the retrieve step
when the ivy.xml file isn't found.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message