You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Ioannis Canellos (JIRA)" <ji...@apache.org> on 2011/09/01 22:14:09 UTC
[jira] [Commented] (KARAF-844) Fix dynamic imports from Cellar
Hazelcast bundle
[ https://issues.apache.org/jira/browse/KARAF-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095574#comment-13095574 ]
Ioannis Canellos commented on KARAF-844:
----------------------------------------
I initially removed the global dynamic import from karaf and replaced that with dynamic imports per cellar module, but since I don't think that anyone would want to install just a part of cellar I will totally remove them.
> Fix dynamic imports from Cellar Hazelcast bundle
> ------------------------------------------------
>
> Key: KARAF-844
> URL: https://issues.apache.org/jira/browse/KARAF-844
> Project: Karaf
> Issue Type: Improvement
> Components: cellar-hazelcast
> Affects Versions: cellar-2.2.2, cellar-2.2.1
> Reporter: Ioannis Canellos
> Assignee: Ioannis Canellos
> Fix For: cellar-3.0.0, cellar-2.2.3
>
>
> The Cellar Hazelcast has a dynamic import on org.apache.karaf.*
> This is not very elegant. Moreover, the samples which usually are packaged under org.apache.karaf.cellar.samples are automatically import and thus become unrealistic (potential class loading issues are not visible in samples).
> The dynamic imports could be more specific or get replaced by optional imports.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira