Return-Path: 
 <notifications-return-2160-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@locus.apache.org
Received: (qmail 65533 invoked from network); 31 Mar 2008 22:22:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 31 Mar 2008 22:22:48 -0000
Received: (qmail 11666 invoked by uid 500); 31 Mar 2008 22:22:48 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 11648 invoked by uid 500); 31 Mar 2008 22:22:48 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 11639 invoked by uid 99); 31 Mar 2008 22:22:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2008 15:22:48 -0700
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Mar 2008 22:22:15 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id BADB1234C0B2
	for <notifications@ant.apache.org>; Mon, 31 Mar 2008 15:20:25 -0700 (PDT)
Message-ID: <527770152.1207002025764.JavaMail.jira@brutus>
Date: Mon, 31 Mar 2008 15:20:25 -0700 (PDT)
From: "Maarten Coene (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Resolved: (IVY-779) resolve fails to put metadata in cache
In-Reply-To: <91717056.1205870244483.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/IVY-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene resolved IVY-779.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0)
                   2.0-RC1

I think I've fixed the problem. Could you give it a try with code from SVN?

> resolve fails to put metadata in cache
> --------------------------------------
>
>                 Key: IVY-779
>                 URL: https://issues.apache.org/jira/browse/IVY-779
>             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
>             Fix For: 2.0-RC1
>
>         Attachments: debug-beta1.log, debug-beta2.log, output-beta1.log, output-beta2.log, sample-project.tar
>
>
> 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.