[UIMA-951] Eclipse split packages not handled well - causing plugin ClassNotFound failures

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.2AS, 2.2.2
• Component/s: Eclipse plugins
• Assignee: Marshall Schor
• Reporter: Marshall Schor
• Created: 28/Mar/08 20:26
• Updated: 02/Apr/08 13:06
• Resolved: 01/Apr/08 21:15

Description

Some eclipse packages are split across multiple bundles. The maven-bundle-plugin, by default, will put in a package import, which could get connected to only one of the bundles. If that bundle doesn't have the class, you get a classnotfound exception. Which bundle gets wired is arbitrary - often differing based on platform, build, etc.

The fix is to identify all the split packages in Eclipse (these can be found by opening the Eclipse HELP and searching using the keywords ( split packages map )). Then for each split package, add a Require-Bundle for each bundle that has some of the classes for that package.

Add the Require-Package directive to the affected POMs to make these stable against possibly wrong wiring.