ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <>
Subject Re: Ivy file not published when using specific configuration
Date Wed, 23 May 2007 08:19:42 GMT
On 5/23/07, Jean-Baptiste Quenot <> wrote:
> Hi there,

Hi JB,

I'm using <ivy:publish>  to publish the artifacts  generated by my
> build to  a local  repository.  This  works well,  until I  had to
> specify conf="default" to avoid  publishing for examples WAR files
> to  the repository  (belongs to  configuration "webapp").   When I
> added this  attribute, Ivy  files stopped  being published  to the
> repository, and building other modules depending on this published
> artifact failed  with the following error  (with anonymized module
> names):
> [ivy:resolve] :: problems summary ::
> [ivy:resolve] :::: WARNINGS
> [ivy:resolve]   problem while downloading ivy file:
> /path/to/local/repo/organisation/artifact/1.0-dev-20070523072416/ivy.xml to
> /var/tmp/ivy51894xml:
> /path/to/local/repo/organisation/artifact/1.0-dev-20070523072416/ivy.xml (No
> such file or directory)
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve]           :: [ organisation | artifact | latest.development]: null
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve]

It's weird. The message is really strange, even though having a problem with
configuration publication is not that surprising (it was introduced in 1.4.1),
the error reported is strange. I guess you have verified that you have a
file at
Because it's the first diagnostic we can see from the warning.

Notice the word "null" at the end of the module descriptor.  This is Ivy
> 1.4.1.

Yes, if I remember correctly, this is likely to be the getMessage() from the
exception raised. In latest Ivy version, we output the exception itself when
the exception has a null message (like NPE for instance). Maybe you could
give Ivy 2.0-alpha1 a try, just to see if you have the same problem and a
better message? It's supposed to be backward compatible, so a drop in
replacement for the test should work.


Your help will be appreciated.
> --
>      Jean-Baptiste Quenot
> aka  John Banana   Qwerty

Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message