Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Mon, 18 Apr 2011 08:16:05 +0000 (UTC)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: 
 <1321089628.63928.1303114565821.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2111084333.6864.1299635339709.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (IVYDE-277) Using workspace dependency resolver,
 project source dirs are not added to dependent project's source lookup path
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

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

       Resolution: Fixed
    Fix Version/s: trunk

No response indeed. Let's close it.

> Using workspace dependency resolver, project source dirs are not added to=
 dependent project's source lookup path
> -------------------------------------------------------------------------=
---------------------------------------
>
>                 Key: IVYDE-277
>                 URL: https://issues.apache.org/jira/browse/IVYDE-277
>             Project: IvyDE
>          Issue Type: Bug
>          Components: launch configuration
>    Affects Versions: 2.1.0
>         Environment: Eclipse Helios
> WinXP
>            Reporter: Chris Birchall
>            Assignee: Nicolas Lalev=C3=A9e
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: ProjectsAandB.zip
>
>
> Apologies if this is a duplicate or just a mistake in my IvyDE settings.
> I have a number of dependent projects in an Eclipse workspace, linked usi=
ng IvyDE's "Resolve dependencies in workspace". I am also using a number of=
 3rd party jars.
> For simplicity of explanation, let's say I have two projects, A and B.=20
> Project A depends on project B and on 3rdparty.jar.
> Project B's class folders are correctly added to project A's classpath, s=
o I can run project A using an Eclipse run configuration with no problems. =
However, project's B's source folders are not added to the run configuratio=
n's source lookup path. Strangely, project B's class folders are added to t=
he path, but of course there are no source files in there.
> This causes problems when debugging project A. If I am stepping through s=
ome Project A code and try to step into a Project B method, Eclipse does no=
t how where to find Project B's source, so it gives me an error. As a worka=
round I have to manually add all of project B's source folders to the looku=
p path.
> Note that the source for 3rdparty.jar is correctly retrieved from the rep=
o and steppable using the debugger. (I notice that it is not added to the s=
ource lookup path, so I guess the debugger can find it as a source attachme=
nt to the jar). Similarly, if I close project B then projectB-src.jar is co=
rrectly retrieved and debuggable.
> =20

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