[jira] [Commented] (IVYDE-277) Using workspace dependency resolver, project source dirs are not added to dependent project's source lookup path

["Chris Birchall (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVYDE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015694#comment-13015694 ] 

Chris Birchall commented on IVYDE-277:
--------------------------------------

Thank you for the fix! But testing with the latest Hudson build of IvyDE, it appears that this bug is not fixed.

I tested with the following versions:

Apache Ivy 2.2.0.final_20110331115717
Apache IvyDE 2.2.0.201104030801-hudson-179

I'm sure you have plenty of tests, but just in case I'll attach two simple projects that you can use to reproduce the bug.

> 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
>            Priority: Minor
>
> 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 using 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. 
> Project A depends on project B and on 3rdparty.jar.
> Project B's class folders are correctly added to project A's classpath, so 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 configuration's source lookup path. Strangely, project B's class folders are added to the path, but of course there are no source files in there.
> This causes problems when debugging project A. If I am stepping through some Project A code and try to step into a Project B method, Eclipse does not how where to find Project B's source, so it gives me an error. As a workaround I have to manually add all of project B's source folders to the lookup path.
> Note that the source for 3rdparty.jar is correctly retrieved from the repo and steppable using the debugger. (I notice that it is not added to the source lookup path, so I guess the debugger can find it as a source attachment to the jar). Similarly, if I close project B then projectB-src.jar is correctly retrieved and debuggable.
>  

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