You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by David Bosschaert <da...@gmail.com> on 2012/07/04 12:36:55 UTC
SPI-Fly ready for inclusion in main Aries build?
Hi all,
I think that the SPI-Fly subproject [1] is getting close to ready for
inclusion in the main Aries build. It is the Reference Implementation
of the OSGi Enterprise R5 'ServiceLoader Mediator' specification [2],
but supports more SPI-style APIs than just ServiceLoader.
I was thinking that it would be good to add it to the 'global' Aries
build as soon as 1.0 is released for org.apache.aries.util and
org.apache.aries.testsupport.unit as these are its 2 aries
dependencies.
Just thinking what else needs to be done for SPI-Fly
* Currently it uses asm 3.2 but IIRC we should update to 4.0 in order
to make it work with Java 7 - haven't tried this but that's what I
heard.
* The documentation at [1] needs to be updated to describe the spec
behaviour as well (currently it only lists the proprietary
configuration).
Anything else?
Cheers,
David
[1] http://aries.apache.org/modules/spi-fly.html
[2] Chapter 133 in http://www.osgi.org/Download/Release5
Re: SPI-Fly ready for inclusion in main Aries build?
Posted by Holly Cummins <ho...@googlemail.com>.
+1 for building spi-fly in the main build, if only for the benefits of
regular testing and regular building.
On Wed, Jul 4, 2012 at 11:36 AM, David Bosschaert
<da...@gmail.com> wrote:
> Hi all,
>
> I think that the SPI-Fly subproject [1] is getting close to ready for
> inclusion in the main Aries build. It is the Reference Implementation
> of the OSGi Enterprise R5 'ServiceLoader Mediator' specification [2],
> but supports more SPI-style APIs than just ServiceLoader.
>
> I was thinking that it would be good to add it to the 'global' Aries
> build as soon as 1.0 is released for org.apache.aries.util and
> org.apache.aries.testsupport.unit as these are its 2 aries
> dependencies.
> Just thinking what else needs to be done for SPI-Fly
> * Currently it uses asm 3.2 but IIRC we should update to 4.0 in order
> to make it work with Java 7 - haven't tried this but that's what I
> heard.
> * The documentation at [1] needs to be updated to describe the spec
> behaviour as well (currently it only lists the proprietary
> configuration).
> Anything else?
>
> Cheers,
>
> David
>
> [1] http://aries.apache.org/modules/spi-fly.html
> [2] Chapter 133 in http://www.osgi.org/Download/Release5