Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 7 Sep 2011 07:53:11 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <278360942.23960.1315381991166.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1918984244.6864.1314887349925.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (KARAF-844) Fix dynamic imports from Cellar
 Hazelcast bundle
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/KARAF-844?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofr=C3=A9 resolved KARAF-844.
----------------------------------------

    Resolution: Fixed

> 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 package=
d under org.apache.karaf.cellar.samples are automatically import and thus b=
ecome unrealistic (potential class loading issues are not visible in sample=
s).
> The dynamic imports could be more specific or get replaced by optional im=
ports.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira