Return-Path: 
 <notifications-return-24054-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
X-Original-To: apmail-ant-notifications-archive@minotaur.apache.org
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5909E11B63
	for <apmail-ant-notifications-archive@minotaur.apache.org>;
 Fri, 25 Apr 2014 14:15:17 +0000 (UTC)
Received: (qmail 88914 invoked by uid 500); 25 Apr 2014 14:15:16 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 88876 invoked by uid 500); 25 Apr 2014 14:15:16 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 88867 invoked by uid 99); 25 Apr 2014 14:15:15 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Apr 2014 14:15:15 +0000
Date: Fri, 25 Apr 2014 14:15:15 +0000 (UTC)
From: "Ulrike M (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: <JIRA.12707162.1396958037318.180991.1398435315833@arcas>
In-Reply-To: <JIRA.12707162.1396958037318@arcas>
References: <JIRA.12707162.1396958037318@arcas>
Subject: [jira] [Comment Edited] (IVY-1467) Resolving results in weird
 working@[localhostname] revisions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/IVY-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981037#comment-13981037 ] 

Ulrike M edited comment on IVY-1467 at 4/25/14 2:14 PM:
--------------------------------------------------------

running target "ivy.resolve.compile" will work fine, but target "ivy.resolve.runTest" will fail with the message described earlier.
IMPORTANT: the failure only happens if the target "ivy.resolve.compile" is run first, followed by  "ivy.resolve.runTest".
If I clean the local ivy cache, and run "ivy.resolve.runTest", no such error occurs (and I may run that target or the compile target as many times as I want afterwards). 


was (Author: ulrikem):
running target "ivy.resolve.compile" will work fine, but target "ivy.resolve.runTest" will fail with the message described earlier.

> 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.2#6252)