[
https://issues.apache.org/jira/browse/UIMA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-951.
-------------------------------
Resolution: Fixed
Tong Fin reports: All the plugins work for me in the following environments:
- Windows: Eclipse 3.3.2, 3.3.1.1, 3.2.2
- Linux: Eclipse 3.3.2, 3.2.2
> Eclipse split packages not handled well - causing plugin ClassNotFound
> failures
> -------------------------------------------------------------------------------
>
> Key: UIMA-951
> URL: https://issues.apache.org/jira/browse/UIMA-951
> Project: UIMA
> Issue Type: Bug
> Components: Eclipse plugins
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.2.2S, 2.2.2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
