Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Received-SPF: pass (athena.apache.org: domain of
 holly.k.cummins@googlemail.com designates 209.85.212.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHEBw=SinrBL-L3iKC2UxTuK8ndGg5iM7bFt4jpObCyjasBX3Q@mail.gmail.com>
References: 
 <CAHEBw=SinrBL-L3iKC2UxTuK8ndGg5iM7bFt4jpObCyjasBX3Q@mail.gmail.com>
Date: Fri, 25 May 2012 14:47:21 +0100
Message-ID: 
 <CAC9tjn9wDsQMm6Jy6zz4R0OXy_=Jg2ng-zx1ra+qHZxJAUYBoA@mail.gmail.com>
Subject: Re: proxy-api needs at least org.osgi.framework 1.6.0
From: Holly Cummins <holly.k.cummins@googlemail.com>
To: dev@aries.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, May 25, 2012 at 2:09 PM, Bal=E1zs Zsoldos
<balazs.zsoldos@everit.biz> wrote:
> Hi,
>
> as I look at it org.apache.aries.proxy.api needs at least
> org.osgi.framework 1.6 which is part of OSGI 4.3. Is it knowingly changed=
?
> Based on this proxy will not work with older OSGI containers (e.g.
> glassfish till version 3.1.1).

I was wondering about this as well. It doesn't seem ideal, does it?
>
> This problem may occurs at other places as well where the osgi.core
> dependency was changed to 4.3.

It looks like the proxy changes were made as part of ARIES-826. I
think the original intention of the weaving code was that it would
still be compatible with OSGi 4.2. I guess our options are to do
something like what we've done with util-42, or split off an optional
advanced.api bundle with the 4.3-dependent classes.

Holly