[announce] peaberry 1.1 released

[Stuart McCulloch]

Hi folks,

I've just released http://peaberry.googlecode.com/files/peaberry-1.1.zip with the following fixes:

  http://code.google.com/p/peaberry/issues/list?can=1&q=label%3ARelease1.1

  17  Implement service registry for Eclipse Extensions  <--  this is an optional add-on bundle
  20  Potential leak in StickyDecorator
  21  Support AOP style interception
  22  OSGiServiceExport: put after unput does not work for the same instance
  24  Expose BundleScope to clients
  25  Ensure cached proxies are flushed from service iterators
  26  Support injection of Eclipse Extensions using Guice
  27  ServiceUnavailableException is cached per proxy class.
  29  Apply decoration more consistently for exported and watched services
  30  Make watching a single() service more intuitive
  32  OSGi bundle should require org.aopalliance.aop package.

The 1.1 artifacts are waiting to be mirrored to Maven central, should appear in a few hours time.

As always, let me know if you have any issues / ideas for new features / want to help out :)

--
Cheers, Stuart

[Rinswind]

Kudos Stuart. Nice to have all the bugfixes uploaded to Maven - frees
me from building and mavenizing manually :)

[Stuart McCulloch]

2009/4/14 Rinswind <Rins...@gmail.com>

Kudos Stuart. Nice to have all the bugfixes uploaded to Maven - frees
me from building and mavenizing manually  :)

no problem, I forgot to also mention that this build has been successfully
tested on Google's AppEngine, using a custom service registry in place
of OSGi... so we just need to get an OSGi framework working there ;)
 

--
Cheers, Stuart

[Will Horn]

The peaberry 1.1 zip includes guice-customloader-20090412. Is it
necessary to use that version of guice? I have the guice 20090205
snapshot build that is on the guice downloads page.

Thanks,
Will

[Stuart McCulloch]

2009/4/18 Will Horn <will...@gmail.com>

The peaberry 1.1 zip includes guice-customloader-20090412.  Is it
necessary to use that version of guice?  I have the guice 20090205
snapshot build that is on the guice downloads page.

yes, you should use the "customloader" patched version because
it contains two patches that weren't in the February snapshot and
which should be in the final release of Guice 2

these patches fix an issue proxying system types under OSGi and
update the internal copy of Google Collections to the 1.0 RC1 level
(the patches are under "lib/build" if you want to apply them yourself)

also you'd probably have a problem using the February snapshot of
Guice because it accidentally bumped the Guice API version up to 2
(even though the API is compatible with 1) which means that it won't
match against the import range of "[1,2)" used in peaberry.

previous Guice snapshots used an API version of 1.0 - I'm not sure
what the Guice team will pick for the final release, but I'd personally
use something like 1.1 to show it's compatible with the 1.0 API, but
has added new features.

[ in OSGi you can version bundles and packages separately, and so
  Guice 2 can let people know that its API is compatible with Guice 1
  while still bumping the main bundle/project version up to 2 ]

HTH

--
Cheers, Stuart