You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Phil Clay (JIRA)" <ji...@apache.org> on 2010/03/03 18:52:27 UTC
[jira] Created: (IVYDE-237) Multiple eclipse projects with similar
ivy library definitions results in launch config source path collisions
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
I have multiple eclipse projects with very similar project structures.
Each eclipse project has an one ivy library pointing to an ivy.xml file at 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 ivy library is exported from each project.
I have "resolve dependencies in workspace" turned on. It works great, the 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 for project D. After some further investigation, this is what I found...
Using the default source lookup path does not include the project D. More on that later.
So, I decided to manually configure the source path. Here's the process I followed:
1. I started by adding project A.
2. Upon adding A, I noticed that two entries appeared in the source lookup 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 the 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 appears.
So, I believe that since each of the ivy libraries are configured the same 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 the source lookup path.
I believe the same is true if I use the default source lookup path (rather than adding projects manually). When looking at the default source lookup path, I can only see a subset of the depend-on projects. Usually, they only include the dependencies of one project, and nothing transitive.
I tried to test this theory by renaming the ivy.xml files to ivy-${projectname}.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 get added, BUT if you try to expand them, you get an error message saying that 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 project 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-237) Multiple eclipse projects with
similar ivy library definitions results in launch config source path
collisions
Posted by "Phil Clay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852976#action_12852976 ]
Phil Clay commented on IVYDE-237:
---------------------------------
Hi Nicolas,
I tried the latest IvyDE from trunk. 2.1.0.201003291630-hudson-102
The default source lookup path looks better.
However I'm still seeing weird behavior when trying to configure the source lookup path manually. I believe it is the same as I saw before.
I believe this will reproduce it...
1) create two projects, each with their own ivy.xml and ivy library in eclipse
2) make sure the ivy library is exported in both projects (Project | Properties | Java Build Path | Order and Export)
3) Create a new launch config
4) Project = projectA (this doesn't really matter, just select one)
On the source tab, remove the default
Add | Java Project | select both projects (ensure "Add exported entries of selected projects" is checked)
Click ok
You will now see 2 projects in the source lookup path, but only one ivy library. You should see 2 projects and 2 ivy libraries.
Let me know if you need more help reproducing it.
> 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
> 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 at 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 ivy library is exported from each project.
> I have "resolve dependencies in workspace" turned on. It works great, the 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 for project D. After some further investigation, this is what I found...
> Using the default source lookup path does not include the project D. More on that later.
> So, I decided to manually configure the source path. Here's the process I followed:
> 1. I started by adding project A.
> 2. Upon adding A, I noticed that two entries appeared in the source lookup 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 the 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 appears.
> So, I believe that since each of the ivy libraries are configured the same 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 the source lookup path.
> I believe the same is true if I use the default source lookup path (rather than adding projects manually). When looking at the default source lookup path, I can only see a subset of the depend-on projects. Usually, they only include the dependencies of one project, and nothing transitive.
> I tried to test this theory by renaming the ivy.xml files to ivy-${projectname}.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 get added, BUT if you try to expand them, you get an error message saying that 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 project 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-237) Multiple eclipse projects with
similar ivy library definitions results in launch config source path
collisions
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850866#action_12850866 ]
Nicolas Lalevée commented on IVYDE-237:
---------------------------------------
Thank you for your detailed report Phil.
I had some trouble with the launch configuration and IvyDE too. I think I have resolved most of the issues I have encountered.
I think there some jira issue I could point you too, but I cannot find them...
Here is the documentation about the launch configuration and IVYDE trunk:
http://ant.apache.org/ivy/ivyde/history/trunk/cpc/launch.html
I would be great if you could try the trunk version of IvyDE (http://ant.apache.org/ivy/ivyde/download.cgi#hudson) and see if it fixes your issues.
> 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
> 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 at 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 ivy library is exported from each project.
> I have "resolve dependencies in workspace" turned on. It works great, the 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 for project D. After some further investigation, this is what I found...
> Using the default source lookup path does not include the project D. More on that later.
> So, I decided to manually configure the source path. Here's the process I followed:
> 1. I started by adding project A.
> 2. Upon adding A, I noticed that two entries appeared in the source lookup 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 the 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 appears.
> So, I believe that since each of the ivy libraries are configured the same 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 the source lookup path.
> I believe the same is true if I use the default source lookup path (rather than adding projects manually). When looking at the default source lookup path, I can only see a subset of the depend-on projects. Usually, they only include the dependencies of one project, and nothing transitive.
> I tried to test this theory by renaming the ivy.xml files to ivy-${projectname}.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 get added, BUT if you try to expand them, you get an error message saying that 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 project 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-237) Multiple eclipse projects with
similar ivy library definitions results in launch config source path
collisions
Posted by "Eric Sirianni (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901856#action_12901856 ]
Eric Sirianni commented on IVYDE-237:
-------------------------------------
Nicolas - any progress on this? I'm having the same problem as Phil.
Basically, this bug makes IvyDE unusable when using a launch configuration that includes more than one java project. Decomposing a java application project into multiple java project modules is one of the main best practices that led to the popularity of Ivy in the first place, so it is unfortunate that this use case does not work with IvyDE.
Do you need any more information on this? If you need any help, care to point me to a location in the IvyDE code?
> 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
> 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 at 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 ivy library is exported from each project.
> I have "resolve dependencies in workspace" turned on. It works great, the 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 for project D. After some further investigation, this is what I found...
> Using the default source lookup path does not include the project D. More on that later.
> So, I decided to manually configure the source path. Here's the process I followed:
> 1. I started by adding project A.
> 2. Upon adding A, I noticed that two entries appeared in the source lookup 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 the 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 appears.
> So, I believe that since each of the ivy libraries are configured the same 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 the source lookup path.
> I believe the same is true if I use the default source lookup path (rather than adding projects manually). When looking at the default source lookup path, I can only see a subset of the depend-on projects. Usually, they only include the dependencies of one project, and nothing transitive.
> I tried to test this theory by renaming the ivy.xml files to ivy-${projectname}.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 get added, BUT if you try to expand them, you get an error message saying that 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 project 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-237) Multiple eclipse projects with similar
ivy library definitions results in launch config source path collisions
Posted by "Phil Clay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Clay updated IVYDE-237:
----------------------------
Attachment: ivyde_source_lookup_5.png
ivyde_source_lookup_5.png shows the result of adding a project to the source lookup path after changing the ivy file names (in every project) to ivy-${projectname}.xml.
dfm-server is the target project for the eclipse launch configuration.
dfm-apiserver is the project that I added to the source lookup path.
Notice that eclipse/ivyde is incorrectly trying to resolve ivy-dfm-apiserver.xml relative to dfm-server (instead of dfm-apiserver)
> 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
> 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 at 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 ivy library is exported from each project.
> I have "resolve dependencies in workspace" turned on. It works great, the 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 for project D. After some further investigation, this is what I found...
> Using the default source lookup path does not include the project D. More on that later.
> So, I decided to manually configure the source path. Here's the process I followed:
> 1. I started by adding project A.
> 2. Upon adding A, I noticed that two entries appeared in the source lookup 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 the 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 appears.
> So, I believe that since each of the ivy libraries are configured the same 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 the source lookup path.
> I believe the same is true if I use the default source lookup path (rather than adding projects manually). When looking at the default source lookup path, I can only see a subset of the depend-on projects. Usually, they only include the dependencies of one project, and nothing transitive.
> I tried to test this theory by renaming the ivy.xml files to ivy-${projectname}.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 get added, BUT if you try to expand them, you get an error message saying that 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 project 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-237) Multiple eclipse projects with similar
ivy library definitions results in launch config source path collisions
Posted by "Phil Clay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Clay updated IVYDE-237:
----------------------------
Attachment: ivyde_source_lookup_4.png
ivyde_source_lookup_3.png
ivyde_source_lookup_3.png show the selection of multiple projects.
ivyde_source_lookup_4.png shows the result of the selection.
Notice that only one ivy library was added, even though every project has an exported ivy library.
> 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
> Attachments: ivyde_source_lookup_1.png, ivyde_source_lookup_2.png, ivyde_source_lookup_3.png, ivyde_source_lookup_4.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 at 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 ivy library is exported from each project.
> I have "resolve dependencies in workspace" turned on. It works great, the 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 for project D. After some further investigation, this is what I found...
> Using the default source lookup path does not include the project D. More on that later.
> So, I decided to manually configure the source path. Here's the process I followed:
> 1. I started by adding project A.
> 2. Upon adding A, I noticed that two entries appeared in the source lookup 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 the 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 appears.
> So, I believe that since each of the ivy libraries are configured the same 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 the source lookup path.
> I believe the same is true if I use the default source lookup path (rather than adding projects manually). When looking at the default source lookup path, I can only see a subset of the depend-on projects. Usually, they only include the dependencies of one project, and nothing transitive.
> I tried to test this theory by renaming the ivy.xml files to ivy-${projectname}.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 get added, BUT if you try to expand them, you get an error message saying that 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 project 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVYDE-237) Multiple eclipse projects with similar
ivy library definitions results in launch config source path collisions
Posted by "Phil Clay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Clay updated IVYDE-237:
----------------------------
Attachment: ivyde_source_lookup_2.png
ivyde_source_lookup_1.png
ivyde_source_lookup_1.png is showing that I selected one project to add.
ivyde_source_lookup_2.png is the result of adding one project.
Notice the project was added, and the ivy library. However, the ivy library references ivy.xml, and that is resolved using the launch configuration path (dfm-server), rather than the project from which the library came (dfm-api)
> 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
> Attachments: ivyde_source_lookup_1.png, ivyde_source_lookup_2.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 at 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 ivy library is exported from each project.
> I have "resolve dependencies in workspace" turned on. It works great, the 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 for project D. After some further investigation, this is what I found...
> Using the default source lookup path does not include the project D. More on that later.
> So, I decided to manually configure the source path. Here's the process I followed:
> 1. I started by adding project A.
> 2. Upon adding A, I noticed that two entries appeared in the source lookup 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 the 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 appears.
> So, I believe that since each of the ivy libraries are configured the same 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 the source lookup path.
> I believe the same is true if I use the default source lookup path (rather than adding projects manually). When looking at the default source lookup path, I can only see a subset of the depend-on projects. Usually, they only include the dependencies of one project, and nothing transitive.
> I tried to test this theory by renaming the ivy.xml files to ivy-${projectname}.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 get added, BUT if you try to expand them, you get an error message saying that 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 project 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVYDE-237) Multiple eclipse projects with
similar ivy library definitions results in launch config source path
collisions
Posted by "Nicolas Lalevée (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVYDE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901861#action_12901861 ]
Nicolas Lalevée commented on IVYDE-237:
---------------------------------------
I haven't had time look at it.
Our source code is available from several places, you will probably be interested in checking our from subversion: http://ant.apache.org/ivy/ivyde/download.cgi#svn
There is also some basic documentation on how to build it: http://ant.apache.org/ivy/ivyde/history/trunk/dev/build.html
> 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
> 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 at 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 ivy library is exported from each project.
> I have "resolve dependencies in workspace" turned on. It works great, the 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 for project D. After some further investigation, this is what I found...
> Using the default source lookup path does not include the project D. More on that later.
> So, I decided to manually configure the source path. Here's the process I followed:
> 1. I started by adding project A.
> 2. Upon adding A, I noticed that two entries appeared in the source lookup 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 the 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 appears.
> So, I believe that since each of the ivy libraries are configured the same 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 the source lookup path.
> I believe the same is true if I use the default source lookup path (rather than adding projects manually). When looking at the default source lookup path, I can only see a subset of the depend-on projects. Usually, they only include the dependencies of one project, and nothing transitive.
> I tried to test this theory by renaming the ivy.xml files to ivy-${projectname}.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 get added, BUT if you try to expand them, you get an error message saying that 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 project 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.
-
You can reply to this email to add a comment to the issue online.