Hi all,
I need some advice on how to use pax:provisioning in order to simplify
deployment of a Maven-built OSGi-based system that I am working on.
The system I am building has several "components", with each component
consisting of several OSGi bundles.
Now, the final system is packaged together in a "mix-and-match" manner
where customer A may only want component X, while customer B wants
components X and Y.
The Maven project is organized as follows (with each bundle being a
separate child module of a component).
+ root/
+ pom.xml
+ component-X/
pom.xml
+ bundle-X-1/
+ bundle-X-2/
...
+ component-Y/
pom.xml
+ bundle-Y-1/
+ bundle-Y-2/
...
I would like to create provisioning pom files for customer A (that
includes all component X bundles plus dependencies), and a
provisioning file for customer B (that includes all component X and Y
bundles plus dependencies).
Now, the question is how would I manage these customer provisioning
files in the most convenient way?
I believe (please correct me if I am wrong) that the most elegant
solution would be to have pom-customer-A.xml include the pom of
component-X as a dependency.
However, pax provisioning does not seem to resolve the component pom's
child module dependencies transitively (it ignores the pom saying "No
bundles found").
Is there a way to directly reference a parent project in such a
manner, without needing to enumerate all child (bundle) projects
explicitly?
Or maybe there is an even better strategy that I haven't thought of?
Any suggestions are welcome!
regards, Peter
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
