You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Ulrike M (JIRA)" <ji...@apache.org> on 2014/04/08 13:56:14 UTC
[jira] [Updated] (IVY-1467) Resolving results in weird
working@[localhostname] revisions
[ https://issues.apache.org/jira/browse/IVY-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ulrike M updated IVY-1467:
--------------------------
Attachment: ivy.log
The failure log
> Resolving results in weird working@[localhostname] revisions
> ------------------------------------------------------------
>
> Key: IVY-1467
> URL: https://issues.apache.org/jira/browse/IVY-1467
> 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
(v6.2#6252)