Hi Siamak,
as far as I know nobody is working on that, it would sure be a nice to
have though! One thing you might want to keep in mind is that bundles
may only be in one deployment package, this could become a problem
quickly if all dependencies are sucked in automatically when generating
a package. On the other hand, for quick convenient testing purposes this
may be exactly what you want... :)
Another approach would be to specify exactly what should be inside the
deployment package manually and have the maven-deployment-plugin create
a valid deployment package out of the specified artifacts. In this case
I think you would not really benefit from using bndlib.
friendly,
Christian
Siamak Haschemi wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello to all,
is someone currently working on a maven-deployment-plugin to produce
OSGi Deployment Packages (*.dp) (like specified in the OSGi Service
Platform Service Compendium, Release 4, Version 4.1, Sec. 114)?
If no, where should I start?
Looking at the maven-bundle-plugin is naturally, but I am insecure if I
should base on the bndlib to use the several classes like "Jar" and
"Manifest" or if such a extended classpath traversing and dependency
checking is needless.
Any hints?
Kind regards,
Siamak Haschemi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkfOs8MACgkQBLvtewtTERN/ngCdGDJMhiOwJXwD5dZWF0Ihexif
22IAoI3QHZeypR2Avxz6y5cRkulZQqEp
=gRHq
-----END PGP SIGNATURE-----
