[
https://jira.jboss.org/jira/browse/JBPM-1995?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1995:
-----------------------------------
this functionality should go in the db module
command to execute this script should be like this
mvn -Djbpm.previous.version=4.0 -Pupgrade clean install
The mvn build should call an ant script. Invocation of that script should be in the
upgrade profile. The ant script should check for the jbpm.previous.version property. If
not set, an exception should be thrown.
The result should be per database in the target directory:
- a script with the upgrade ddl
- a schema diff file
build script to calculate jBPM DB differences
---------------------------------------------
Key: JBPM-1995
URL:
https://jira.jboss.org/jira/browse/JBPM-1995
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Heiko Braun
Assignee: Joram Barrez
Fix For: jBPM 4.1
1) automated script that
* gets the jbpm schema create scripts from a (configured) previous version from jbpm
from the maven repo.
* create previous version schema in db (preferably leverage existing jdbc.properties
handling)
* run the hibernate update tool to calculate DDL upgrade script
* optionally add the capability of running the test suite against the migrated DB
schema
2) in one go it is probably easy to add an automatic diff report between the plain sql
ddl schema generation scripts. that can be used to verify if there are any other changes
then the ones that hibernate distills in the schema update tool
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira