Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Sun, 3 Apr 2011 11:38:05 +0000 (UTC)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: 
 <124548779.31085.1301830685680.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (IVYDE-237) Multiple eclipse projects with
 similar ivy library definitions results in launch config source path
 collisions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/IVYDE-237?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalev=C3=A9e resolved IVYDE-237.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: trunk
         Assignee: Nicolas Lalev=C3=A9e

I think I finally understand what the launch configuration expects from Ivy=
DE and I have implemented it. It seems to work a lot better now. I'll appre=
ciate some feedback on the fix.

> Multiple eclipse projects with similar ivy library definitions results in=
 launch config source path collisions
> -------------------------------------------------------------------------=
-------------------------------------
>
>                 Key: IVYDE-237
>                 URL: https://issues.apache.org/jira/browse/IVYDE-237
>             Project: IvyDE
>          Issue Type: Bug
>          Components: launch configuration
>    Affects Versions: 2.0.0.final
>         Environment: Ubuntu 8.10, Eclipse 3.5.2, IvyDE 2.0.0.final
>            Reporter: Phil Clay
>            Assignee: Nicolas Lalev=C3=A9e
>             Fix For: trunk
>
>         Attachments: ivyde_source_lookup_1.png, ivyde_source_lookup_2.png=
, ivyde_source_lookup_3.png, ivyde_source_lookup_4.png, ivyde_source_lookup=
_5.png
>
>
> I have multiple eclipse projects with very similar project structures.
> Each eclipse project has an one ivy library pointing to an ivy.xml file a=
t the root of each the project.  (i.e. one ivy.xml file per project)
> The projects have various dependencies on each other, going three or four=
 deep.  (e.g. A depends on B, B depends on C, C depends on D, etc).  The iv=
y library is exported from each project.
> I have "resolve dependencies in workspace" turned on.  It works great, th=
e build time project dependencies are resolved properly.  Love this!  But, =
I think the same thing applies if I have this turned off.
> The problem happens when creating a launch configuration.  I noticed this=
 when debugging.  I created a launch configuration pointing at project A.  =
When stepping through a debug session, eclipse could not find the sources f=
or project D.  After some further investigation, this is what I found...
> Using the default source lookup path does not include the project D.  Mor=
e on that later. =20
> So, I decided to manually configure the source path.  Here's the process =
I followed:
> 1. I started by adding project A. =20
> 2. Upon adding A, I noticed that two entries appeared in the source looku=
p path
>     - the project A itself
>     - the ivy library of the project
> 3. Now I add project B
> 4. Upon adding B, I noticed that only one additional entry appeared in th=
e source lookup path
>    - the project B itself
> The ivy library of project B did not appear (even though it is exported)
> Similarly, if I add all the projects in one step, only one ivy library ap=
pears.
> So, I believe that since each of the ivy libraries are configured the sam=
e way (Essentially pointing to an identically named file in each project), =
that eclipse or IvyDE is getting confused and only adding one of them to th=
e source lookup path.
> I believe the same is true if I use the default source lookup path (rathe=
r than adding projects manually).  When looking at the default source looku=
p path, I can only see a subset of the depend-on projects. Usually, they on=
ly include the dependencies of one project, and nothing transitive.
> I tried to test this theory by renaming the ivy.xml files to ivy-${projec=
tname}.xml.  This makes all of the ivy libraries unique, since the ivy xml =
file name is included as part of the library definition.  However, now if I=
 add multiple projects to the source lookup path, multiple ivy libraries ge=
t added, BUT if you try to expand them, you get an error message saying tha=
t the ivy-${projectname}.xml file doesn't exist (because it is looking for =
that xml file in the root of the launch config project, rather than the pro=
ject from which the library is coming from.
> I can easily reproduce this behavior, so let me know if you need further =
information

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira