Updates:
Status: Invalid
Comment #1 on issue 612 by [email protected]: Problematic profile
activation in extensions-parent
http://code.google.com/p/google-guice/issues/detail?id=612
This dependency is correct - the extensions need to compile against the
pre-jarjar'd build of Guice before they are jarjar'd themselves. This
particular build artifact is not uploaded to Maven central to avoid people
depending on it by mistake, but because it's an optional dependency (used
only at compile time) it won't affect people using the individual extension
artifacts.
The bug here is in the bundleall goal of the maven-bundle-plugin which
appears to ignore the optional setting on the dependency and treats it as
required. Personally I would avoid using the bundleplugin's bundleall goal
and use something like Embed-Dependency to wrap jars into bundles, because
a) the specific bundleall goal is no longer maintained b) the bundles it
creates have poor OSGi metadata and c) you lose the inter-dependency
information between the wrapped bundles.
PS Guice and its extensions already have OSGi metadata already and don't
need to be "bundlized".
--
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.
