Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Hans Lund <hlu@multi-support.com>
To: "<ivy-user@ant.apache.org>" <ivy-user@ant.apache.org>
Subject: Re: ivy:publish on ivy-2.3.0
Thread-Topic: ivy:publish on ivy-2.3.0
Thread-Index: AQHOIYMJR1CNXi74GUiV2KjWkkiYC5imxL+AgAAlaq4=
Date: Fri, 15 Mar 2013 16:03:11 +0000
Message-ID: <35B0D572-F9BF-462E-B921-033FE0684BA0@multi-support.com>
References: 
 <FF8DD4FE4E32634CB29827B22C5CF0011F1DADD3@msexch01.multi-support.lan>,<514334ED.2050100@reast.net>
In-Reply-To: <514334ED.2050100@reast.net>
Accept-Language: en-US, da-DK
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hey Jayson

I did find your issue, and speculated that it could be related. The symptom=
 however is a bit different.=20
In our case we depend on junit latest.revision in a test configuration - bu=
t have junit as transitive dependency for junit 3.8.2 within the compile de=
pendencies. Resolve and retrieve fetches junit 4 ( which we depend on in ou=
r tests) but in the published ivy our direct test dependency on junit repla=
ces the latest.revision with 3.8.2 and not the required junit 4+ dependency=
.

/Hans Lund=20

On 15/03/2013, at 15.49, "Jason R-J" <jason_ivy@reast.net> wrote:

> On 15/03/2013 13:43, Hans Lund wrote:
>> Hi
>>=20
>> After upgrading from ivy-2.2.0 to ivy-2.3.0 I'm running into problems wi=
th ivy:publish.
>>=20
>> The problem is that after the upgrade, the revisions in the published iv=
y.xml no longer is the same as the ones resolved.
>> Of cause this only happens in conjunction with conflict resolving (and p=
erhaps only when using latest strategies) not really tested that.
>> The effect is that  trying to compile the published artifact source arti=
fact can't compile, using the published ivy - but can using my source ivy.
>>=20
>> I'm not sure if this is a bug or change of behavior eg:
>>=20
>> Does publish use a configuration and do an internal resolve? or does it =
use latest resolve ? Has that changed.
>>=20
>> Best Regards
>> Hans Lund
> Hi Hans,
>=20
> I spotted a similar issue which I reported[1], could this be similar situ=
ation for you?
>=20
> Jason
>=20
> [1] https://issues.apache.org/jira/browse/IVY-1410