[MGNLMIGRATION-252] Upgrade to 4.5 gives NoClassDefFoundError on PurExtraConfigTask Created: 25/Jul/13 Updated: 16/Sep/15 Resolved: 19/Sep/14 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | Migration Task |
| Affects Version/s: | 1.2.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Gordon Bentvelzen | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows, Jetty, Magnolia 4.5.9 |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Date of First Response: | |||||||||||||
| Visible to: |
Edgar Vonk
|
||||||||||||
| Description |
|
When I try to upgrade from 4.4.11 to 4.5.9 using latest 1.2.4-SNAPSHOT version (magnolia-4-5-migration-1.2.4-20130724.135205-42) the migration task shows the error: 2013-07-25 15:20:08,705 INFO gnolia.migration.reporting.DefaultReportingService: Starting migration of extends definition for the following module:public-user-registration |
| Comments |
| Comment by Robert Šiška [ 26/Jul/13 ] |
|
Hello Gordon, The extra migrations tasks were decided to be moved to the modules themselves. Robert |
| Comment by Gordon Bentvelzen [ 26/Jul/13 ] |
|
Hello,
Yes. The release of 4.5.10 is planned for end of July, that means this week. We suggest to upgrade!
Well, I didn't find any problems with parsing the Freemarker templates, but bear in mind that you will Cheers, |
| Comment by Gordon Bentvelzen [ 30/Jul/13 ] |
|
Hello Robert, Ok, thanks, I will upgrade when it 4.5.10 is released! Did you actually manage to upgrade the Worldsteel freemarker templates? I'm having a bit of trouble though with configuring the Migration Tool. See: http://jira.magnolia-cms.com/browse/SUPPORT-2593 I tried using the script as Rich mentioned, but the interface of the TemplateScriptMigrationTask in the Groovy script doesn't seem to match with the the Java class: Groovy: GroovyRuntimeException: Could not find matching constructor for: info.magnolia.migration.task.templates.TemplateScriptMigrationTask(java.lang.String, java.util.LinkedHashMap, java.util.LinkedHashMap, java.lang.Boolean) Java: public TemplateScriptMigrationTask(String moduleName, String templatesPath, Map siteDefinitions, boolean generateScripts) Could you have a look? Thanks, you can close this issue then! |
| Comment by Robert Šiška [ 30/Jul/13 ] |
|
The Groovy scripts don't work because they were meant to be removed before 1.2.4 release... Did the tool page caused any problems? Looking at your support ticket, I would first update Btw, if you back-up your ftl files and tick "Generate groovy scripts instead of migrating right away", it's not such an one-time process I haven't try to migrate your whole project yet, I'll try once I find a moment. Robert |
| Comment by Gordon Bentvelzen [ 30/Jul/13 ] |
|
Ok, thanks! I'll give your settings a try. That is, the internet site definition also extends the default-worldsteel site definition. Should I include the default-worldsteel as well, when migrating the internet templates? Ah ok Gordon |
| Comment by Gordon Bentvelzen [ 30/Jul/13 ] |
|
Robert, I tried your settings on the Migration Tool and it seems to work fine. But although I checked the box 'Generate Groovy scripts instead of migrating right away', the Migration Tool did change the templates when I clicked the button 'Run Migration', and also created a directory templating-kit.bak containing the original templates. Is that the expected behaviour? You find the resulting migration report attached. If that's not the case, then maybe it's best to close this issue, and/or start new one(s) when necessary. Thanks, |
| Comment by Robert Šiška [ 19/Sep/14 ] |
|
The 'Generate Groovy scripts instead of migration right away' option was removed. The backup mechanism is implemented instead. |
| Comment by Michael Mühlebach [ 16/Sep/15 ] |
|
This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again. |