[
https://issues.apache.org/jira/browse/IVY-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190786#comment-14190786
]
Miroslav Zaťko commented on IVY-1467:
-------------------------------------
Hi all,
same problem here...
I just noticed, in my cache in ivy-1.7.7.xml & ivy-1.7.6.xml definitions for
modules jul-to-slf4j, log4j-over-slf4j & jcl-over-slf4j, there is dependency on
module "slf4j-api" rev="working@wrkstat-01"
> 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, ivy.zip
>
>
> 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.3.4#6332)
