You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "David Goblirsch (JIRA)" <ji...@apache.org> on 2015/09/24 00:00:05 UTC
[jira] [Created] (IVY-1533) Build seems to work, but lots of
warning messages about 'impossible to put metadata file in cache'
David Goblirsch created IVY-1533:
------------------------------------
Summary: Build seems to work, but lots of warning messages about 'impossible to put metadata file in cache'
Key: IVY-1533
URL: https://issues.apache.org/jira/browse/IVY-1533
Project: Ivy
Issue Type: Bug
Affects Versions: 2.4.0
Environment: RedHat 6.5 enterprise linux
Reporter: David Goblirsch
Just upgraded from ivy 2.3 to ivy 2.4. Seems to work fine, but even though the end results of the build appear to be the same as when using 2.3, the log is now peppered with lots of warnings of the form
impossible to put metadata file in cache: [filename]
for the ivy:resolve task, raising a 'FileNotFoundException' for files with a
name following this pattern:
.ivy2/cache/[org]/[name]/ivy-[yyyyMMddHHmmss].xml.original
where [org] is the org of a dependency, [name] is the name of the
dependency.
The complaint is for our local jars which do not have version numbers.
It is not observed (yet) for 3rd-party jars having version numbers.
That is, if I build 3 of our local jars A, B, C, and then build a jar D that
depends on those, the log for D complains 3 times about 'impossible to put metadata file in cache: ', for files named ivy-[timestamp].xml.original,
one message for each of the libraries A, B and C.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)