Community
Participate
Working Groups
I have a workspace that contains two plugin projects (A and B). They both have source folders src and lib, but B/lib is a linked source folder pointing to A/lib (the folder contains library code shared by the two plugins). This arrangement works fine for editing, compiling and testing the two plugins. However, an attempt to export project B fails. The plugin.xml's runtime page lists both source folders as contributors to the plugin jar file (which works properly for project A, and for B if the linked source folder is replaced by a non-linked one); with the linked source folder however, an error occurs complaining that the source folder does not exist. This is on Eclipse 3.0. The export happens via a Feature project that lists project B as one of the plugin projects making up the feature.
*** This bug has been marked as a duplicate of 66177 ***