Description Jeff McAffer 2011-06-29 12:41:25 EDT

Created attachment 198842 [details]
projects that demonstrate the problem

Steps:
- import the attached projects into a workspace
- notice that there are no compile errors
- export the folder.feature to /temp/exploded.  This will also export the folder.bundle as well.
- close folder.feature and folder.bundle projects
- notice there is a compile error in folder.test 
- open the test.target file in folder.test.  Modify the lone software site entry to include the newly exported folder.feature.  You may be able to just press Update.
- Set test.target as the current target
- notice that the compile errors still exist.

This should work but does not.  If you look in the <workspace>/.metadata/plugins/org.eclipse.pde.core/bundlepool area you will see that folder.bundle is there as a folder and has all the right content.  The folder.test manifest does not show any errors (so the folder.bundle) appears to have been found and is satisfying the require bundle dependency.  inspection of all the relevant metadata and artifact info shows everything to be in good order. (at least by my eye)

Now work around this problem by 
- delete the folder.bundle dir in the bundle pool and the export destination folder (just to be sure)
- reopen the folder.bundle and folder.feature projects
- edit the folder.bundle manifest to have Bundle-Classpath: .   (that is, '.' on the bundle's classpath)
- re-export and redo the target as above
- notice now that folder.test has NO compile errors.


if you have a p2 repo that contains dir shaped bundles