On Thursday 29 June 2006 23:38, Jason van Zyl wrote:
> I took a quick look at the OSGi plugin that you guys have and I
> quickly tried to hack it up so that the standard Maven Jar plugin
> used some of the logic to add the appropriate manifest entries.
Thanks for the interest. _I_ am not entirely sure what you are actually trying
to achieve and what the request really is.
Out of all the code for the plugin, very little is duplicated work, although
there are a couple of lines.
More important issue, IMHO, is the general <configuration> tag for plugins,
which can't at all be decoupled from the <plugin> declaration. Many OSGi
projects consists of a lot of bundles, and having a lot of duplication of
both the plugin declaration as well as common manifest entries makes each
bundle's pom fairly extensive, even if it doesn't really need to be.
I forked[1] the Maven OSGi plugin to allow me to put these entries as
<properties> entries in the pom instead, which made the project poms very
nimble. That change has not made it into the Felix version.
What would be cool is a 'extension' mechanism for the configuration section of
a plugin. Not sure how it should look like, but where it is possible to
override configuration elements of the parent pom's plugin declaration with
additional or new values, and without deeply nested XML elements.
Cheers
Niclas
[1] Source is available at;
https://scm.ops4j.org/repos/ops4j/projects/pax/maven/osgi-bundle/
