Hey all,
So… this sucks rocks, but sadly, the OSGI metadata included in 3.0 is
broken - not in a way that inhibits guice core, but for using any of the
extensions in an OSGI environment.
The bottom line is this -
http://code.google.com/p/google-guice/issues/detail?id=494. The missing
Eclipse-ExtensibleAPI: true property from the OSGI metadata means that anyone
using guice's extensions in a variety of osgi contexts is broken unless they
repackage guice and the extension into their own osgi bundle. In order to make
my own such project work, I need to build a local version of guice including
that fix (or depend on other people's repackaging of guice).
I propose a 3.0.1 bug-fix release that simply updates the metadata.
Basically a branch from 3.0 as-released with mcculls' patch pulled in. I wish I
could just update the metadata on maven central repo, but released artifacts
are, as we all probably know, write-once.
So… any objections to rolling 3.0.1 as-described. And if not… are there
any critical bug-fixes that have made their way in that are worth cherry
picking? This is not a release from head, so I'd rather keep it to a minimum,
but just in case people have urgent things they feel are worth the trouble.
cheers,
Christian.
----
Christian Edward Gruber - Senior Software Engineer - Java Core Libraries - Guice
Google :::: +1 (646) 807-9839 [US] :::: +1 (647) 737-9839 [CA] ::::
[email protected]
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-guice-dev?hl=en.
