Hey Will

Regarding your inplace templating issue, this has already been fixed [1]. 
However, you will have to define the dependency to the newer released version 
of inplace templating in your pom:
[code]
<dependency>
    <groupId>info.magnolia</groupId>
    <artifactId>magnolia-module-inplace-templating</artifactId>
    <version>1.3.2</version>
</dependency>
[/code]

I haven't come across the installation problem with the migration tool though 
and I've been using the released 1.2(.0) version of the module to migrate a 
4.4.6 project. 

HTH
Cheers
Natascha

[1] http://jira.magnolia-cms.com/browse/MGNLINTEMPL-24

On Jan 8, 2013, at 10:24 PM, Will Scheidegger wrote:

> Dear Magnolians, dear Samuel
> 
> We're trying to migrate a Magnolia 4.4.9 EE installation to 4.5.7, and (as 
> expected) it's still a bumpy ride. Since I'm expecting many more bumps to 
> come I called this thread "Migration Troubles I", giving me room for II, III 
> etc. :-/
> 
> We've tried to follow the documentation [1] to the letter, although not easy 
> all the time:
> - We've updated our code which now compiles fine with Magnolia 4.5.7 (step 3 
> [2])
>       - Strange enough although we did remove the taglib dependencies they 
> still end up in our webapp (but that's not really a show stopper)
>       - We also removed the dependency to magnolia-module-templating, but 
> still find magnolia-module-templating-4.5.7.jar in the webapp (again no 
> biggie)
> - We've also updated the security in the webapp and repository and the node 
> types (step 4 [3])
>       - The single line documentation to "Update the node types" leave a lot 
> of room for interpretation even with the additional info in the link. We 
> reckoned that we had to add the new node types to the custom_nodetypes.xml 
> file, right? Copied them from a plain vanilla 4.5.7 installation... hoping we 
> did the right thing.
> - Went on to step 5 to restart
>       - The documentation [4] would make you believe that after completing 
> step 4 you should be able to start up Magnolia and the migration tasks in the 
> version handler should kick in.
>       - The Update process actually does take quite some time, but then fails 
> with:
>               "Could not install or update magnolia-4-5-migration module. 
> Task 'Trigger migration scripts' failed. (IOException: Can't find resource 
> file at /scripts/migration/from4_4To4_5/ConfiguredMigration.groovy)"
>         and
>               "Could not install or update inplace-templating module. Task '' 
> failed. (IOException: Can't find resource to bootstrap at 
> src/main/resources/info/magnolia/module/inplacetemplating/setup/config.modules.observation.config.listenerConfigurations.versionResourceOnChange.xml)"
> 
> The migration module is 1.3-SNAPSHOT. Should we try with 1.2 or are we 
> missing something else?
> 
> Thanks for helping us clear things up!
> -will
> 
> 
> [1] http://wiki.magnolia-cms.com/display/DEV/How+to+migrate+your+project
> [2] 
> http://wiki.magnolia-cms.com/display/DEV/Updating+your+project+configuration+and+code
> [3] 
> http://wiki.magnolia-cms.com/display/DEV/Updating+the+repository+and+the+webapp
> [4] http://wiki.magnolia-cms.com/display/DEV/Running+the+Migration+module
> 
> 
> ----------------------------------------------------------------
> 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]>
----------------------------------------------------------------

Reply via email to