Hi Lars

Thanks for your answers.
By moving the webapp, I meant to just extract the webapp folder in "webapps"
(e.g. "magnoliaAuthor") and put it into the corresponding "webapps"
directory of a Mgnl-4.5-Installation.
However, what I did then was to install my module jar and the migration
module both into a fresh 4.5.6 and go on from there. But still I had to do a
lot of work by hand, for instance because the migration script could not
find some of my templates and it was some try & error exercise to edit the
Configuration groovy script. I know it's documented a bit, but still there
are a huge amount of options to edit and if it's not entirely clear what
they do, this can steal a lot of time.

Regards
Cedric

-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]] Im Auftrag von Lars Fischer (via
Magnolia Forums)
Gesendet: Montag, 5. November 2012 11:24
An: Magnolia User List
Betreff: [magnolia-user] Re: Migration from 4.4.8 to 4.5.6

Hi Cedric,

see my answers below.

[quote]
-          "Remove magnolia-module-templating module" -> Remove whole
module
too, right? Because the subtitle says "Update your project pom.xml file"
[/quote]

Yes, remove the module.

[quote]
-          "Add a dependency to magnolia-module-migration" -> It's
actually
named "magnolia-4-5-migration", is that correct?
[/quote]

Correct, see
http://git.magnolia-cms.com/gitweb/?p=modules/4-5-migration.git;a=summary

[quote]
-          "In the migrated script we add the cmsUtilTaglib taglib by
default. A dependency to magnolia-templating-jsp is then required." ->
What does this mean?
[/quote]

During the migration process, the cmsUtilTaglib will be added to your
templating scripts (Freemarker and JSP) automatically. If you're using JSP
templates, you have to add the magnolia-templating-jsp dependency.

[quote]
-          I compared the default magnoliaAuthor magnolia.properties of
4.4.8 and they were exactly identical. So in which case do we need to modify
them?
[/quote]

According to your Magnolia version, you should check the following settings
ins magnolia.properties:

* Make sure you have magnolia.bootstrap.samples=false in your configuration
* also set magnolia.update.stkMigration=false

AFAIK the stkMigration flag is false by default starting with 4.5.6 and
obsolete starting with 4.5.7.

In addition to that, there are [b]new[/b] properties in the 4.5.x versions
of Magnolia:

* magnolia.home
* magnolia.author.key.location
* magnolia.service.contact

These need to be added to your configuration. Please have a look at the
magnolia.properties file located in the WEB-INF/config/default folder of a
bundled Magnolia if you don't find the properties in the configuration of
your project.

[quote]
-          This is a class of 4.5, right? If I change it, Magnolia 4.4 does
not restart anymore. Should I change it and manually move my webapp to 4.5
and start it from there?
[/quote]

In web.xml, the listener class and the context-param entries have changed,
you need to adjust at least the listener-class in your project's web.xml. 
What dou you mean by manually moving the webapp?

As of version 4.5.7 of Magnolia, the whole migration process has improved
significantly and the docs will be updated to reflect these changes. You can
have a preview of how this will work here:
[url]http://dev.magnolia-cms.com/blog/2012/10/sprint-7-migration-tool-1-2/[/
url]

HTH
Lars

--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=39eaf1c8-d1a2-490b-
8389-f68503d76411


----------------------------------------------------------------
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