You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2008/03/28 21:28:24 UTC
[jira] Created: (UIMA-951) Eclipse split packages not handled well
- causing plugin ClassNotFound failures
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.
[jira] Resolved: (UIMA-951) Eclipse split packages not handled well
- causing plugin ClassNotFound failures
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor resolved UIMA-951.
---------------------------------
Resolution: Fixed
plugins need testing on linux/windows, and eclipse 3.3.2 and 3.2.x
> 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.
[jira] Commented: (UIMA-951) Eclipse split packages not handled
well - causing plugin ClassNotFound failures
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583770#action_12583770 ]
Marshall Schor commented on UIMA-951:
-------------------------------------
Testing shows this now works on 3.3, but something's not working on 3.2 (both Linux and Windows). Investigating further
> 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.
[jira] Closed: (UIMA-951) Eclipse split packages not handled well -
causing plugin ClassNotFound failures
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ 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.
[jira] Reopened: (UIMA-951) Eclipse split packages not handled well
- causing plugin ClassNotFound failures
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor reopened UIMA-951:
---------------------------------
Reopening - after Tong pointed out that if a package is both in the import-package and require-bundle, then the import-package takes precedence and the require-bundle is ignored. Fix by excluding the split packages from the import-package.
> 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.
[jira] Updated: (UIMA-951) Eclipse split packages not handled well
- causing plugin ClassNotFound failures
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Baessler updated UIMA-951:
----------------------------------
Fix Version/s: (was: 2.2.2S)
2.2.2AS
> 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.2AS, 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.