Community
Participate
Working Groups
Build ID: I20070517-1700 Steps To Reproduce: 1. Fresh workspace 2. Check out org.eclipse.team.tests.core from dev.eclipse.org 3. The project needs some other project in order to build (eg. org.eclipse.compare.tests). The message is: "Cannot resolve plug-in: org.eclipse.compare.tests" Do you think that we can provide a Quick Fix which tries to checkout a required project from the same repo? Using example above: Quick Fix would try to checkout Compare/Tests project using the same repo settings as Team/Tests project has.
This is a fairly complex problem. The simplest solution would be to provide API to obtain the project of the given name from the same repository as the project with the error. This would require a fairly specific Team-level API and would not work every time (i.e. the project may actually come from a different repository or may even only be available from an update site). I doubt we will ever have a Team/Update API in place that would support such a QuickFix. On the up side, the Buckminster project is attempting to tackle to issue of workspace provisioning. This may reduce the need for this type of feature in PDE.
PDE is not in the business of trying to find bundles. In order for this to work consistently for everyone, PDE would need to recursively search every folder in your repository for all the META-INF/MANIFEST.MF files. We could try to search for folder name, but that does garuntee you a resolution. This could be an empty folder with nothing which would do nothing except clutter your workspace. Even if we assumed the project name matches the Bundle-SymbolicName, we still would have do go through and do recursive searches. I know many teams who have their plug-ins in subdirectories under HEAD and not at the base. Lastly, we could not account for plug-ins which are kept in different branches like javax.servlet. The project in HEAD won't do you any good; you need to check it out from a branch. There is no way we can search all the branches to find these plug-ins. This problem is too complicated for PDE to handle so until the TEAM component can come through with some amazining repositiory search capabilities, we are not going to fix this.
