Ensuring db backwards compatibility
Folks,
The recent 3.3.0.GA release is not backward compatible to 3.2.2 with respect to the database layout. As a result of this, the release cannot be used as a drop in replacement for the SOA platform (i.e. the 3.3.0.GA tag cannot be merged to the respective SOA branch). This however is very important in order to reduce maintenance costs.
In other words, it should be easy to maintain http://anonsvn.jboss.org/repos/jbpm/jbpm3/branches/jpdl-3.2.2-SOA-4.2 because the team will have to do it for five years.
To fix this, I propose the following
#1 Setup the dbs that are used for QA with DLL scripts from last SOA tag.
#2 Modify the jbpmtest user privileged to disallow DDL statements
#3 Make the generated DLL scripts part of the SVN codebase
#4 Provide update DLL scripts as a mandatory release artefact
In that way, it is ensured that the QA always runs against a defined database layout which is backward compatible. Create schema scripts have a distinct revision and changes can easily be tracked. Future jBPM3 releases can be easily merged to the SOA branch. Customer issues can be fixed in trunk and become available in the SOA branch with the next release.
First, I would like to have a look at the DLL scripts generated by the last SOA tag and compare them to ones produced by the 3.3.0.GA release. There seems however to be a problem with the build of these SOA tags. Specifically, the builds seem to reference SNAPSHOT versions of the EAP.
get.jboss.dependencies: [get] Getting: http://porkchop.redhat.com/devel/candidates/JBEAP4.3.0/latest/zip/jboss-eap-4.3.0-0.2.beta4.ep1.1.zip [get] To: /home/tdiesler/jbpm/repository/jbossas/4.3.0.GA/lib/jboss-eap.zip [get] Error opening connection java.io.FileNotFoundException: http://porkchop.redhat.com/devel/candidates/JBEAP4.3.0/latest/zip/jboss-eap-4.3.0-0.2.beta4.ep1.1.zip [get] Error opening connection java.io.FileNotFoundException: http://porkchop.redhat.com/devel/candidates/JBEAP4.3.0/latest/zip/jboss-eap-4.3.0-0.2.beta4.ep1.1.zip
Here is the related issue https://jira.jboss.org/jira/browse/SOA-1003