ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srinath Ponnamudi (JIRA)" <>
Subject [jira] [Commented] (IVY-1467) Resolving results in weird working@[localhostname] revisions
Date Mon, 21 Jul 2014 15:04:39 GMT


Srinath Ponnamudi commented on IVY-1467:

Hi Shikhar,

When will this fix going to live. When is the next expected release date?

> Resolving results in weird working@[localhostname] revisions
> ------------------------------------------------------------
>                 Key: IVY-1467
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.4.0-RC1
>            Reporter: Ulrike M
>         Attachments: ivy.log,
> I wanted to give 2.4.0-RC1 a try and ran into this issue. See the log for details.
> I stripped down the case to the bare minimum of what causes the error. If i specify the
following dependencies, resolving conf='
> runtime' will fail with "unresolved dependencies":
> <dependency org="org.slf4j" name="slf4j-api" rev="1.7.7" conf="compile->default"
>     <dependency org="org.slf4j" name="slf4j-log4j12" rev="1.7.7" conf="runtime->default"
> (...)
> :: log4j#log4j;working@PIT11: not found
> (...)
> we are separating compile-time dependencies (slf4j-api) from runtime dependencies (slf4j-log4j12);
this must be specified as two dependencies (as far as I know).
> The funny thing is that if I alter the version of slf4j-api to "1.7.6", clear the ivy
cache and resolve again, it will work smoothly. Version 1.7.6 of slf4j-api will simply get
evicted (as expected).

This message was sent by Atlassian JIRA

View raw message