As long as Module A is installed when Module C is also installed, this works perfectly, since Module A will be resolved along Module C when C is started.
Regards Felix Triquoit Mathieu schrieb: > I have two bundles which defines a kind of framework... Let's say Module A > and Module B. > In a Module C I have : > <Import-Package>packagenameModuleA;version=2.0.*</Import-Package> > > If I send to my customer with the file-install plugin, I cannot assume (if I > have all the bundles in the deployment directory) that the module A will be > started before B before C. > I don't know if it is clear ? > > Is there a way ? > > Thanks, > Mathieu > > 2009/6/12 Toni Menzel <[email protected]> > >> Can you explain why ? >> In OSGi you should never depend on deployment order. Because of that >> there is no api to do this. >> Can you explain why you need this order ? >> Then we might solve it here "the right way". >> >> cheers, >> Toni >> >> On Fri, Jun 12, 2009 at 3:39 PM, Triquoit >> Mathieu<[email protected]> wrote: >>> Hi, >>> >>> Is there a way to order the deployment ? When I want to publish to my >>> customer a fresh version, I cannot order the deployment but I have some >> kind >>> of dependencies between some modules ? >>> >>> I would like to write somewhere deploy Module A or somethink like : >> "don't >>> deploy Module B before module A" ? >>> >>> Thanks in advance, >>> Best regards, >>> Mathieu >>> >> >> >> -- >> Toni Menzel >> Independent Software Developer >> Professional Profile: http://okidokiteam.com >> [email protected] >> http://www.ops4j.org - New Energy for OSS Communities - Open >> Participation Software. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
