Hi, Am 10.07.2012 um 15:27 schrieb Völschow, Rainer:
> Hello Felix, > > the order reflects a hirachy from the bundles. I took a look into the console > and figured out some bundles contains some dependenciess from others. Yes, this is the OSGi capability and requirements graph mostly reflected through the Import-Package and Export-Package statements. There is no need to deploy in order because OSGi does a amazingly good job at resolving the dependencies. Particularly in conjunction with tooling such as Apache Sling OSGi Install (included with Adobe CQ) or Apache Felix Fileinstall come in handy here: Those tools install bundles and try hard to start them. > Honestly, as concerned as development with CQ5 and Maven I was being kicked > into cold water. So I'm not fimilar with all yet. No here's the shameless plug: you might consider looking at the Adobe CQ training offerings ;-) Regards Felix PS: I will refrain from talking about Adobe CQ in this list now. > > By the way, tips and hints are always welcome. :-) > > Regards > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[email protected]] > Im Auftrag von Felix Meschberger > Gesendet: Dienstag, 10. Juli 2012 14:31 > An: OSGi Developer Mail List > Betreff: Re: [osgi-dev] Bundles in a bundle > > Hi, > > Am 10.07.2012 um 10:30 schrieb Völschow, Rainer: > >> Hello, >> >> thanks for replying. The background is following: >> >> At my work I use the conent manaagement system "Communiqué Day" -Short CQ- >> in version 5. For deploying code it uses the implementation of Apache Felix. >> The purpose is it to make it easier for the Administrator deploying services >> in correct order and for automatically activation. So I want to wrap the >> main bundles into another bundle. > > Yikes: What is the background to require deployment order ? > > (Since I work for Adobe I can give you another hint: if you deploy with a > content package as is usual for Adobe CQ applications, the Apache Sling OSGi > Installer (part of Adobe CQ) will make sure all bundles are deployed and > started. There is even a Maven plugin to generate such content packages) > > Regards > Felix > >> >> Regards >> reporter >> >> >> >> Achtung, schützen wir unsere Umwelt: Müssen Sie diese Mail wirklich >> ausdrucken? >> >> >> Allgemeiner Wirtschaftsdienst Gesellschaft für Wirtschaftsberatung und >> Finanzbetreuung mbH >> Rechtsform: GmbH, Sitz der Gesellschaft: Hannover, Registergericht: AG >> Hannover, Registernummer: HRB 55324 >> Geschäftsführer: Götz Wenker (Vorsitzender), Thomas Bilitewski, Jens Dieter, >> Dr. Stephan Kaufmann >> >> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte >> Informationen. >> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich >> erhalten haben, >> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. >> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht >> gestattet. >> >> ________________________________________ >> Von: [email protected] [mailto:[email protected]] >> Im Auftrag von Raymond Auge >> Gesendet: Montag, 9. Juli 2012 18:02 >> An: OSGi Developer Mail List >> Betreff: Re: [osgi-dev] Bundles in a bundle >> >> 2012/7/9 Völschow, Rainer <[email protected]> >> Exists a way to create a bundle, that contains onther bundles? And if so how >> can I achive this? >> >> Can you explain the reason you would want to do that? >> >> I can think of three possible ones, each has a very different answer. All of >> them involve artifacts within artifacts as the absolute last course of >> action (and only for one or two very specific reasons). >> >> So some clarification would help to get you the correct one. >> >> Sincerely, >> -- >> Raymond Augé | Senior Software Architect | Liferay, Inc. >> --- >> 8-9 October 2012 | Liferay North America Symposium | >> liferay.com/northamerica2012 >> 16-17 October 2012 | Liferay Europe Symposium | liferay.com/europe2012 >> 24-25 October 2012 | Liferay Spain Symposium | liferay.com/spain2012 >> >> >> >> >> _______________________________________________ >> OSGi Developer Mail List >> [email protected] >> https://mail.osgi.org/mailman/listinfo/osgi-dev > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
