Hi Natascha Thanks for the help. As I said, I'm used to run Groovy scripts from the scripts repository (using the scripts dialog), not from the console. Therefore I asked if I had to manually create them in the scripts repository. But running them from the console is fine with me.
Two things I still don't understand: 1. In the documentation, what does the first line at each step mean, e.g. "Groovy class: TemplatesAndParagraphsToPagesAndComponentsWorkspace: configMandatory: yes" It tells me in what Groovy class things happen, but as you said: The migration methods are called from Migration.groovy so what can/should I make with the info above. 2. Is it possible to start with a fresh 4.5.1, add my modules, bootstrap and call the Migration.groovy script with only my module added to the module collections in the script? I'm getting tons of exceptions and not getting anywhere here. Still feeling ignorant :-( -will On 13.03.2012, at 11:24, Natascha Desmarais wrote: > Hello Will > > The way we used it is referencing all necessary steps and scripts from the > main script called Migration.groovy and this script will be automatically > executed on installation of the migration module (see extraInstallTasks of > info.magnolia.templatingkit.migration.setup.STKMigrationVersionHandler). > > However, you should also be able to launch it from the groovy console. The > important thing to know about this is really that everything happens in > Migration.groovy and you often cannot simply run the other scripts > independently since they expect ids/paths/etc from previously executed > scripts. > Not sure if I really understand your first question though. You will have to > checkout this module, adapt the scripts to your needs (release the module if > needed) and restart your instance with this module. While installing it will > write all the migration steps into log/the console so you can see what it is > currently working on (the migration of the content usually takes the longest). > Don't hesitate to point out more things like these. We worked on it for a > long time so we know where to find what, but it is hard to figure out what > needs more documentation for people who see these scripts for the first time > :) and to be fair, it is pretty complex. > > HTH > Natascha > > On Mar 13, 2012, at 11:07 AM, Will Scheidegger wrote: > >> I'm feeling quite ignorant today, but I'm still not sure if I'm doing things >> the way they were intended :-/ >> >> In [1] (and following paragraphs) the user is being told to run Groovy >> scripts for the migration process. >> >> The way I work with Groovy scripts is to create a script and hit the run >> button in the script dialog. However... >> a) The scripts don't seem to get created by the bootstrap process. Is it >> really the idea to create them manually? >> b) Even after reading [2] I still don't know how to trigger the scripts as >> described in [3]. Do you do this on the Groovy CLI? >> >> Any help to lessen my ignorance is warmly appreciated! >> -will >> >> >> [1] >> http://wiki.magnolia-cms.com/display/DEV/Migration+process+of+module+configuration+and+websites#Migrationprocessofmoduleconfigurationandwebsites-Introductiontothemigration >> [2] http://documentation.magnolia-cms.com/modules/groovy.html >> [3] >> http://wiki.magnolia-cms.com/display/DEV/Migration+process+of+module+configuration+and+websites#Migrationprocessofmoduleconfigurationandwebsites-1.Move > > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
