Community
Participate
Working Groups
Using I20060110-1026 or I have 2 projects, one is a plugin and a the other is a fragment of that plugin. I exported each to an archive file. I import (existing project into workspace) each (plugin first, then fragment) into another workspace. After I import the fragment, classes referenced from the plugin are not resolved in the fragment, but should be since they are exported in the manifest of the plugin. I was able to create a simplified test case that I will attach (2 zip files). I think this may be happening in the case that there is no plugin activator class specified. I couldn't replicate when I had a plugin activator class.
I forgot to mention that if you close/open the 2 projects then the bogus errors go away. Also, I was able to replicate this in I20060119-0800.
Created attachment 33481 [details] plugin zip
Created attachment 33482 [details] fragment zip
right. this happens when a fragment declares its own dependencies. *** This bug has been marked as a duplicate of 109335 ***
