...
Both framework and plugin2 have new versions. DeltaShell has to find to 1.2 to 1.3 mappings for framework and 1.1 to 1.2 mappings for plugin2. Since not all entity mappings change the logic is as follows.
Per mapping file
1 Try to find exact match for the version that is in the db. So for entity River of Plugin2 try to find the mapping river.hbm.1.1.xml
2 If this is not found try to find the first earlier version and use this.
3 If none found use the 'normal' hbm.xml.
If the version of the project file is older than the oldest legacy hbm this version is not supported and a message should be shown. For example you have a db 0.4 but mappings only support back to 0.6. So 0.4 is no longer supported and the load cannot continue. So in a flowchart :
This section and the implemented logic has been updated June 2012
The rule per mapping file is simple:
- Take the first mapping file with a version equal or more recent than the persisted version.
More elaborate, in a chart:
So how does this affect plugin development?
...