[
http://jira.magnolia-cms.com/browse/MGNLMIGRATION-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Lipp updated MGNLMIGRATION-7:
------------------------------------
Description:
When upgrating from 4.4.6 to 4.5 we have the possibility to run the migration
script within the upgrade process, or to perform a normal module upgrade (from
4.4.6 to 4.5) and later call the migration script from the Groovy console.
This issue only happens in the second case.
The first step of the migration process is to move and rename nodes (for
example: Component templates (former paragraphs) to config:<module
name>/templates/components).
In this case, we will face (tons of) WARNings like:
2012-03-12 12:43:42,593 WARN
gnolia.content2bean.impl.Content2BeanProcessorImpl: can't resolve class for
node /modules/standard-templating-kit/templates/stkArticle
java.lang.ClassNotFoundException:
info.magnolia.module.templatingkit.templates.STKTemplate
....
In fact info.magnolia.module.templatingkit.templates.STKTemplate does not
exist any more.
IMPORTANT.
Once the migration script ended and Magnolia's restarted, the migrated Magnolia
is running fine.
was:
When upgrating from 4.4.6 to 4.5 we have the possibility to run the migration
script within the upgrate process (working fine), or to perform a normal
upgrate (from 4.4.6 to 4.5) and then call the migration script from the Groovy
console.
This issue happen in this case.
The first step of the migration process is to move and rename nodes (for
example: Component templates (former paragraphs) to config:<module
name>/templates/components).
In this case, we will face the following WARN
2012-03-12 12:43:42,593 WARN
gnolia.content2bean.impl.Content2BeanProcessorImpl: can't resolve class for
node /modules/standard-templating-kit/templates/stkArticle
java.lang.ClassNotFoundException:
info.magnolia.module.templatingkit.templates.STKTemplate
....
We will have tons of warn.
In fact info.magnolia.module.templatingkit.templates.STKTemplate does not
exist any more.
IMPORTANT.
Once the migration script ended and Magnolia's restarted, the migrated Magnolia
is running fine.
> Content2BeanProcessorImpl exceptions when running the migration script from
> the Groovy Console
> ----------------------------------------------------------------------------------------------
>
> Key: MGNLMIGRATION-7
> URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-7
> Project: Magnolia Migration
> Issue Type: Bug
> Affects Versions: 1.0.1
> Environment: CE and EE.
> Reporter: Eric Hechinger
> Assignee: Eric Hechinger
> Priority: Major
> Fix For: 1.1
>
>
> When upgrating from 4.4.6 to 4.5 we have the possibility to run the migration
> script within the upgrade process, or to perform a normal module upgrade
> (from 4.4.6 to 4.5) and later call the migration script from the Groovy
> console.
> This issue only happens in the second case.
> The first step of the migration process is to move and rename nodes (for
> example: Component templates (former paragraphs) to config:<module
> name>/templates/components).
> In this case, we will face (tons of) WARNings like:
> 2012-03-12 12:43:42,593 WARN
> gnolia.content2bean.impl.Content2BeanProcessorImpl: can't resolve class for
> node /modules/standard-templating-kit/templates/stkArticle
> java.lang.ClassNotFoundException:
> info.magnolia.module.templatingkit.templates.STKTemplate
> ....
> In fact info.magnolia.module.templatingkit.templates.STKTemplate does not
> exist any more.
> IMPORTANT.
> Once the migration script ended and Magnolia's restarted, the migrated
> Magnolia is running fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
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]>
----------------------------------------------------------------
