In my opinion the best option is to always install through the repository, either through a content package as you indicated, or by doing a PUT of the bundle directly to its location in the repository using Sling. Also check out http://adamcin.net/vltpack-maven-plugin/index.html - its a maven plugin that will automate a lot of this for you.
Paul McMahon Acquity Group ________________________________ From: "Rudolph, Dirk" <[email protected]> To: [email protected] Cc: "Koenig, Thomas" <[email protected]>; "Schlag, Rene" <[email protected]> Sent: Wednesday, May 29, 2013 3:22 AM Subject: Best practise of deploying bundles during development Hi all, what ist he best way deploying bundles during development? In our project we have two possibilities. On the one hand building a content package that is deployed including all bundles and on the other hand we use the maven-sling-plugin to install bundles directly to the webconsole. Using both at the same time causes errors sometimes (like service configuration bound to wrong service due to changing Bundle-Locations, ...). Additionally I mentioned that the last released version of the maven-sling-plugin depends on the old sling 2.0 API. Is there a new release planned for the current API version? Thanks a lot, Dirk Rudolph T-Systems Multimedia Solutions GmbH Organisationseinheit CCS Dirk Rudolph Software-Entwicklung, OCJP Hausanschrift: Riesaer Straße 5, 01129 Dresden Postanschrift: Postfach 10 02 24, 01072 Dresden +49 351 2820-5363 (Tel) E-Mail: [email protected] <mailto:[email protected]> Internet: http://www.t-systems-mms.com <http://www.t-systems-mms.de/> T-Systems Multimedia Solutions GmbH Aufsichtsrat: Klaus Werner (Vorsitzender) Geschäftsführung: Peter Klingenburg, Dr. Jens Nebendahl Handelsregister: Amtsgericht Dresden HRB 11433 Sitz der Gesellschaft: Dresden Ust-IdNr.: DE 811 807 949
