Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 nicolas.lalevee@hibnet.org does not designate 216.86.168.182 as permitted
 sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: IvyDE seems to prefer artifacts in non-workspace-resolver over
 projects present in workspace
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: 
 <CAB2fYyNr3kvRfchdzAdMoG9b805meXx-XkJezg+-JhZJQE=HvA@mail.gmail.com>
Date: Mon, 14 May 2012 22:28:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C886CC9-151D-4F31-8B22-488CCA069EA4@hibnet.org>
References: 
 <CAB2fYyO2AfWD-nqbFq2-Q3NnsVpTRgYonoTwhFFgdkQroJ8Acw@mail.gmail.com>
 <CAB2fYyNr3kvRfchdzAdMoG9b805meXx-XkJezg+-JhZJQE=HvA@mail.gmail.com>
To: ivy-user@ant.apache.org

Maybe there are some transitive dependency which confuse the Workspace =
resolver. See at the end of the doc:
=
http://ant.apache.org/ivy/ivyde/history/latest-milestone/cpc/workspace.htm=
l

> In some setup, if you want to mix some resolver of your own and the =
workspace resolver, and still want the transitive dependencies work =
nicely between them, you may want to turn the resolve mode to dynamic:
> 	=95 see the defaultResolveMode attribute of settings in the =
ivysettings.
> 	=95 see the resolveMode attribute of module in the ivysettings.

Nicolas

Le 14 mai 2012 =E0 20:36, Matt Hurne a =E9crit :

> On Mon, May 14, 2012 at 2:31 PM, Matt Hurne <matt@thehurnes.com> =
wrote:
>> We are using Ivy to manage the dependencies of our projects on each
>> other, and we're planning to use IvyDE as well.  One of the resolvers
>> we have in our Ivy configuration is used to publish our build
>> artifacts to a local repository (with status "integration") so that
>> they are available when building the projects that depend on them.  =
In
>> a clean environment, this repository is initially empty.  If the =
local
>> repository is empty and we configure IvyDE to resolve dependencies in
>> the workspace, the projects do end up in the Ivy classpath containers
>> of the projects that depend on them as expected.  However, if we then
>> build and publish the projects to the local repository and then
>> perform a new resolve-all in Eclipse/IvyDE, the projects are removed
>> from the Ivy classpath containers and the artifacts in the local
>> repository take their places.
>>=20
>> Is this behavior expected/correct?  Is there a way to ensure that
>> IvyDE will always put workspace projects in the classpath container
>> rather than artifacts with identical module revision IDs that exist =
in
>> one of our configured repositories?
>>=20
>> If I were dealing with this type of scenario outside of =
Eclipse/IvyDE,
>> I would look at putting the resolvers into a chain and using the
>> "returnFirst" attribute to enforce a specific order.  That's
>> effectively what I'm looking to do with the workspace resolver.  Is
>> that possible?
>=20
>=20
> I should have mentioned the following details about our environment:
>=20
> Windows XP 32bit
> Eclipse 3.7 Indigo
> IvyDE 2.2.0.beta1 with Ivy 2.2.0 (we had some other show-stopping
> issues when using IvyDE with Ivy 2.3.0, so we installed Ivy 2.2.0
> explicitly)
>=20
> In addition, when building projects using Ant we're using Ivy 2.2.0.
>=20
> Thanks,
> Matt Hurne