Oh, this is a cool plugin! Thanks for pointing this out!
A few questions...
If I have some default values, can I declare these in a parent POM, or
some kind of config file?
There are some manifest entries that are not processed by the plugin, so
it seems. Is there a reason for this, or have they just not yet been
implemented.
Thanks!
On Mon, 2006-09-25 at 16:57 +0800, Edward Yakop wrote:
> Including the OSGI bundle manifest, assuming the project packaging is
>
> 1. osgi-bundle?
> There is no known option on how to do this. Instead, OSGI
> properties can be defined as
>
> pom.xml:
> <project>
> <packaging>osgi-bundle</packaging>
> ...
> <properties>
> <osgi-ExportPackage>
> org.ops4j.pax.cm.agent;version=${pom.version},
> ...
> </osgi-ExportPackage>
> <osgi-IgnorePackage>
> // List of packages that should be ignored by import
> </osgi-IgnorePackage>
> </properties>
> </project>
>
> 2. normal (i.e. as jar)?
> http://maven.apache.org/guides/mini/guide-manifest.html
>
> Hope this helps.
>
> Regards,
> Edward
>
>
>
> On 9/25/06, David Leangen <[EMAIL PROTECTED]> wrote:
> >
> > I've finally started to make the switch from the ancient DPML Magic
> > build system to M2.
> >
> > How do you guys go about including the OSGi bundle manifests?
> >
> >
> > Thanks!
> > Dave
> >
> >
> >
> >
> > _______________________________________________
> > general mailing list
> > [email protected]
> > http://lists.ops4j.org/mailman/listinfo/general
> >
>
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
