You'll probably find its best to package your bundle as part of your application along with the /content
, /apps
portions of your application in the /apps/myapp/install
folder will cause the libraries to be installed as bundles by the jcr installer provider.
There are a couple of ways of automating packaging/deployment of applications using maven described in these articles:
- http://www.cognifide.com/blogs/cq/maven-plugin-automating-deployments-of-crx-cq-applications/
- http://mkalugin-cq.blogspot.co.uk/2012/11/how-to-use-maven-project-to-create.html
- http://labs.sixdimensions.com/blog/dklco/2012-05-03/introducing-cq-deploy-maven-plugin-deploying-cq-projects
- http://dev.day.com/docs/en/cq/current/core/how_to/how_to_use_the_vlttool/vlt-mavenplugin.html
Alternatively, you could just use the CRXDE to place the bundles and then CRX Package Manager to test the approach, them move on to automated packaging later.
If you don't want to repackage the two OSGI bundles, you can use the sling maven plugin to install the jackson bundle directly
mvn org.apache.sling:maven-sling-plugin:install-file -Dsling.file=jackson-databind-2.2.2.jar