Return-Path: 
 <ivy-user-return-7949-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
X-Original-To: apmail-ant-ivy-user-archive@www.apache.org
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E444248F8
	for <apmail-ant-ivy-user-archive@www.apache.org>;
 Wed,  8 Jun 2011 12:10:14 +0000 (UTC)
Received: (qmail 59551 invoked by uid 500); 8 Jun 2011 12:10:14 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 59522 invoked by uid 500); 8 Jun 2011 12:10:14 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 59486 invoked by uid 99); 8 Jun 2011 12:10:14 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2011 12:10:14 +0000
X-ASF-Spam-Status: No, hits=1.0 required=5.0
	tests=SPF_HELO_PASS,SPF_SOFTFAIL
X-Spam-Check-By: apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 nicolas.lalevee@hibnet.org does not designate 216.86.168.182 as permitted
 sender)
Received: from [216.86.168.182] (HELO mxout-07.mxes.net) (216.86.168.182)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2011 12:10:08 +0000
Received: from [10.0.0.208] (unknown [84.14.57.122])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by smtp.mxes.net (Postfix) with ESMTPSA id 5DDA022E253
	for <ivy-user@ant.apache.org>; Wed,  8 Jun 2011 08:09:44 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: IvyDE Workspace Resolver
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: <31799813.post@talk.nabble.com>
Date: Wed, 8 Jun 2011 14:09:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <70D8CF9F-EB30-43C7-BFFF-BD69ED06F2F4@hibnet.org>
References: <31425340.post@talk.nabble.com> <31431375.post@talk.nabble.com>
 <CBEC97DA-071F-40F2-A734-EAB775C4515F@hibnet.org>
 <31439403.post@talk.nabble.com> <31689250.post@talk.nabble.com>
 <31784151.post@talk.nabble.com>
 <EB5C6266-610B-4810-ACF4-18E4867BBDF6@hibnet.org>
 <31799813.post@talk.nabble.com>
To: ivy-user@ant.apache.org
X-Mailer: Apple Mail (2.1084)


Le 8 juin 2011 =E0 13:36, efe4it a =E9crit :

>=20
>=20
> Nicolas Lalev=E9e wrote:
>>=20
>> About how the workspace resolver work, you have to understand that =
IvyDE
>> is then trying to see the eclipse workspace as an Ivy repository. So =
the
>> ivy.xml files in the Eclipse project must have enough information so =
that
>> it really looks like a repository. The only difference should be =
about the
>> artifacts. Since there is nothing actually published, IvyDE doesn't =
really
>> care about the <publications> tag in the ivy.xml. But you should not
>> reference any artifact in the dependencies section.
>>=20
>> Nicolas
>>=20
>=20
> My IVY file now looks like this (every module is asame, just change =
the name
> of module and artefacts)
> Here my module "win32registry" depends on my other module "exception".
>=20
>=20
>=20
>> <ivy-module version=3D"1.0">
>>    <info organisation=3D"org.efe4it" =
module=3D"efe4it-lib-win32registry"
>> revision=3D"trunk"/>
>>    <configurations>
>>    	<conf name=3D"main-compile" description=3D"compilation of main =
source
>> tree"/>
>>    	<conf name=3D"javadoc" description=3D"documentation"/>
>>    	<conf name=3D"test-compile" description=3D"compilation of test =
source
>> tree"/>
>>    	<conf name=3D"runtime" extends=3D"main-compile" =
visibility=3D"private"
>> description=3D"run"/>
>>    	<conf name=3D"test" extends=3D"test-compile,runtime" =
visibility=3D"private"
>> description=3D"test"/>
>>    </configurations>
>>    <publications>
>>    	<artifact name=3D"efe4it-lib-win32registry-main" type=3D"jar"=20
>> conf=3D"main-compile" ext=3D"jar"/>=20
>> 	<artifact name=3D"efe4it-lib-win32registry-javadoc" =
type=3D"javadoc"
>> conf=3D"javadoc" ext=3D"zip"/>
>>    </publications>
>>    <dependencies>
>>        <dependency org=3D"org.slf4j" name=3D"slf4j" rev=3D"1.5.8"
>> conf=3D"main-compile,javadoc->core"/>
>>        <dependency org=3D"org.slf4j" name=3D"slf4j" rev=3D"1.5.8"
>> conf=3D"runtime->log4j"/>
>>        <dependency org=3D"org.junit" name=3D"junit" rev=3D"4.5"
>> conf=3D"test-compile,test->default"/>
>>        <dependency org=3D"org.efe4it" name=3D"efe4it-lib-exception"
>> rev=3D"trunk" conf=3D"main-compile->main-compile"/>
>>    </dependencies>
>> </ivy-module>
>>=20
>=20
> And ivy console verbose output is
>=20
>=20
>> IVYDE: calling resolve on ivy.xml
>>=20
>> :: resolving dependencies :: =
org.efe4it#efe4it-lib-win32registry;trunk
>> 	confs: [main-compile, test, test-compile, runtime]
>> 	validate =3D true
>> 	refresh =3D false
>> resolving dependencies for configuration 'main-compile'
>> =3D=3D resolving dependencies for =
org.efe4it#efe4it-lib-win32registry;trunk
>> [main-compile]
>> [...]
>> =3D=3D resolving dependencies
>> =
org.efe4it#efe4it-lib-win32registry;trunk->org.efe4it#efe4it-lib-exception=
;trunk
>> [main-compile->main-compile]
>> efe4it-lib-win32registry-ivyde-workspace-chain-resolver: Checking =
cache
>> for: dependency: org.efe4it#efe4it-lib-exception;trunk
>> {main-compile=3D[main-compile]}
>> 	found org.efe4it#efe4it-lib-exception;trunk in
>> efe4it-lib-win32registry-ivyde-workspace-resolver
>> [...]
>> :: resolution report :: resolve 296ms :: artifacts dl 16ms
>> 	=
---------------------------------------------------------------------
>> 	|                  |            modules            ||   =
artifacts   |
>> 	|       conf       | number| search|dwnlded|evicted|| =
number|dwnlded|
>> 	=
---------------------------------------------------------------------
>> 	|   main-compile   |   2   |   1   |   1   |   0   ||   3   |   =
0   |
>> 	|       test       |   4   |   1   |   1   |   0   ||   9   |   =
0   |
>> 	|   test-compile   |   1   |   0   |   0   |   0   ||   3   |   =
0   |
>> 	|      runtime     |   3   |   1   |   1   |   0   ||   6   |   =
0   |
>> 	=
---------------------------------------------------------------------
>> WARN: 	::::::::::::::::::::::::::::::::::::::::::::::
>> WARN: 	::          UNRESOLVED DEPENDENCIES         ::
>> WARN: 	::::::::::::::::::::::::::::::::::::::::::::::
>> WARN: 	:: org.efe4it#efe4it-lib-exception;trunk: configuration =
not found
>> in org.efe4it#efe4it-lib-exception;trunk: 'main-compile'. It was =
required
>> from org.efe4it#efe4it-lib-win32registry;trunk main-compile
>> WARN: 	::::::::::::::::::::::::::::::::::::::::::::::
>>=20
>>=20
>> :: problems summary ::
>> :::: WARNINGS
>> 		::::::::::::::::::::::::::::::::::::::::::::::
>>=20
>> 		::          UNRESOLVED DEPENDENCIES         ::
>>=20
>> 		::::::::::::::::::::::::::::::::::::::::::::::
>>=20
>> 		:: org.efe4it#efe4it-lib-exception;trunk: configuration =
not found in
>> org.efe4it#efe4it-lib-exception;trunk: 'main-compile'. It was =
required
>> from org.efe4it#efe4it-lib-win32registry;trunk main-compile
>>=20
>> 		::::::::::::::::::::::::::::::::::::::::::::::
>>=20
>=20
> If I follow you, having IvyDE ignoring the publication section make
> module-exception "main" JAR not visible to module-win32registry.

Ivy doesn't build anything, so Ivy won't produce that "main" jar. It is =
ant which is doing that. In Eclipse, no jar is not build neither. The =
trick to make your project win32registry compile without having that =
"main" jar, is to make a dependency between the two projects. That is =
what IvyDE is doing with the workspace resolver.

So the resolve on win32registry is about:
* reading the ivy.xml of win32registry : Ivy finds a dependency on =
efe4it-lib-exception;trunk[main-compile]
* looking for efe4it-lib-exception;trunk[main-compile] in the =
repositories
* the first repository to look for is the workspace
* it should find the ivy.xml of the Java project efe4it-lib-exception =
and should see that the version match
* resolved finished it gather every artifacts and add them to the =
classpath. For the ivy.xml resolved via the workspace resolver, the =
artifact is an eclipse project.


> I'm afraid that would mean I need a distinct ivy file for =
Eclipse/IvyDE.
>=20
> If you can spare some time, you may have a broader view of my setup =
here
> (from tomorrow on, some things are actually broken now that I will fix
> tonight):
>=20
>=20
>> svn checkout http://efe4it-suite.googlecode.com/svn/trunk/
>> efe4it-suite-read-only=20
>>=20

your ivy.xml files looks fine to me. I have been able to make a proper =
resolve in workspace (I removed every dependency and I used a default =
ivysettings). Try to clean your caches.
If you still have issues, their maybe an issue in your ivysettings, =
which is not on svn (yet ?).

Nicolas