[
http://jira.magnolia-cms.com/browse/MGNLFORM-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MGNLFORM-138:
----------------------------------
- you are adding update task to version 1.4 in version 1.4.4. Is this correct?
When someone updates from say 1.4.2 to 1.4.4, this task will never get
executed. Is this alright? If so it needs to be documented and explained why
it's ok.
- migration module dependency is not defined in module descriptor, so the
installation order will be random. Is this ok? If so, pls make sure it's
documented in the ticket.
- new bootstrap file was added to {{mgnl-bootstrap}} but it is not bootstrapped
manually during update. How is this configuration change then handled on update?
> Update Pom dependency & Version Handler in order to use the new migration
> process
> ---------------------------------------------------------------------------------
>
> Key: MGNLFORM-138
> URL: http://jira.magnolia-cms.com/browse/MGNLFORM-138
> Project: Magnolia Form Module
> Issue Type: Task
> Affects Versions: 1.4.3
> Reporter: Eric Hechinger
> Assignee: Eric Hechinger
> Fix For: 1.4.4
>
>
> Add dependency on the POM to the migration module.
> Create a new version handling task in order to migrate configuration.
> Add an Extra Migration sub Task (Post Migration specific task).
--
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: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
