Bug 421024

Description Anthony Hunter 2013-11-04 16:50:51 EST

In Orion 3.0, the legacy metadata storage was used and there was no orion.core.metastore property.

In Orion 4.0, there is a orion.core.metastore property.
If property orion.core.metastore=legacy was set, the legacy metadata storage was used.
If property orion.core.metastore=simple was set, the new simple metadata storage was used.
If property orion.core.metastore was not set, the legacy metadata storage was used.
The administrator had to physically set orion.core.metastore=simple to use the new simple metadata storage. Migration was done if there exists a securestorage/user_store.

In Orion 5.0, we want the default to be the simple metadata storage.
If property orion.core.metastore=legacy is set, the legacy metadata storage is used.
If property orion.core.metastore=simple is set, the simple metadata storage is used.
If property orion.core.metastore not set, the simple metadata storage should now be used.
We do not want automatic migration however, since that would modify the project folders on disk with out the administrator's knowledge.
We want the administrator to give permission that a migration can occur by setting orion.core.metastore=simple, just like in Orion 4.0.
So if orion.core.metastore is not set and either of securestorage/user_store or .settings/Users.prefs exist, complain with an error message that the legacy metadata storage is deprecated, point to the migration wiki document and still use legacy metadata storage with these existing files.