configure() executed twice using peaberry activation

[mcculls]

Originally reported on Google Code with ID 76

I noticed that when using the peaberry activation extension the configure() method on
the Bundle-Module class is exectuted twice on starting the bundle. Although harmless,
configure() does not have side effects, it is unexpected.

What steps will reproduce the problem?

1. Load peaberry & peaberry-activation modules
2. Load a bundle specifying a Bundle-Module in it's manifest.

What is the expected output? What do you see instead?

Expected configure() to be executed once, instead it is executed two times.

What version of the product are you using? On what operating system?

I'm using peaberry 1.3 and Felix 4.0.3 with Oracle's java 7u10 Linux jvm, x64 edition
on Ubuntu

Please provide any additional information below.

None.

Reported by merlijn@streamconsulting.nl on 2013-01-11 11:22:56

[mcculls]

#4 alleviates some of these issues by using the TOOL stage when doing the first-pass analysis. Note that the only way to totally remove the need for the two-pass setup would be to use the Guice SPI to analyze, augment, and then replay the binding elements - as I do in https://github.com/eclipse/sisu.inject/blob/master/org.eclipse.sisu.inject/src/org/eclipse/sisu/wire/WireModule.java#L75