Hi, you can use one of the mentioned solutions in this thread, I personally prefer posting to the web console (the default of the Sling maven plugin) as this provides the fastest turnaround during development.
If this results in problems on your installation, like unbound configurations, then there is something else wrong - posting to the web console does a bundle update - basically the same as the OSGi installer does if you put it into the repository. And in this case bundle location isn't changed and configs should still be bound. Regards Carsten 2013/5/29 Rudolph, Dirk <[email protected]> > 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 > > > > > > -- Carsten Ziegeler [email protected]
