Dear XWiki devs
Within the scope of our XWiki-based project called celements, we are using
several so-called "modules", which consist of JARs, web resources
(VM/CSS/JS files) and hibernate mappings. These modules extend the
functionality of the base application and can be optionally added if
required. We need to update and migrate these modules independently from
XWiki. Therefore we require to store individual migration version numbers
in the database for each module.
XWiki's single implementation of
DataMigrationManager, HibernateDataMigrationManager, isn't intended to
store multiple version numbers with specific identifiers in the database.
There also doesn't seem to be an evident hook from XWiki to seamlessly add
own implementations of the DataMigrationManager to the application to
allow migration subsystems.
Considering the similarities of XWiki extensions to our modules, is there
already a way that we have missed to achieve independent migrations of our
modules? If not, are there any future plans from XWiki's side to add this
functionality?
Thanks in advance
Marc Sladek
synventis gmbh