Version handler uses outdated code that might break the installation if
magnolia.update.stkMigration is present in magnolia.properties
--------------------------------------------------------------------------------------------------------------------------------------
Key: MGNLMIGRATION-203
URL: http://jira.magnolia-cms.com/browse/MGNLMIGRATION-203
Project: Magnolia Migration
Issue Type: Bug
Affects Versions: 1.2
Reporter: Natascha Desmarais
Priority: Major
Fix For: 1.2.1
{{info.magnolia.templatingkit.migration.setup.Magnolia45MigrationModuleVersionHandler}}
still uses some outdated code and references a non existing file in the 1.2
branch.
Under certain circumstances, when there is a magnolia.update.stkMigration
properties present in any magnolia.properties, the installation of the module
will fail with
{code}
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)
{code}
This is due to the fact that the {{getExtrasInstallTasks}} function still
references an old file that doesn't exist anymore in the 1.2 version of this
module. Looking closer at the whole VH, it should be revised and updated to not
even consider the property {{magnolia.update.stkMigration}} since this has been
removed altogether.
--
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]>
----------------------------------------------------------------
