Hi
can someone explain the magnolia way of injecting updates into a 
distributed development environment?

At the moment we have no productive release. When we're deploying our first 
release everything should be bootstrapped to the latest version. Therefore 
Magnolia simply imports the XML exports in myModule.jar/mgnl-
bootstrap/myModule/*. How can I preserve the order of the imports?

And now the question about the VersionHandler. Our developers don't want to 
bootstrap every time new updates come in. Changes in the JCR are distributed 
as a VersionHandler delta via our version control system. Theses changes are 
obviously the same JCR-exports which are used for bootstrapping. At the moment 
we extend the DefaultModuleVersionHandler and register a task for every 
version. Theses tasks do nothing more than importing the correct set of these 
JCR export files.

My question is, is this the correct Magnolia way of distributing JCR-changes?

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to