java.lang.Object | |
↳ | com.atlassian.confluence.upgrade.AbstractUpgradeManager |
Known Direct Subclasses |
Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
buildNumberComp | |||||||||||
log |
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
This is the build number of the current version that the user is running under.
| |||||||||||
This is the build number of the data in the database.
| |||||||||||
The is the build number of the new version of Confluence being upgraded to.
| |||||||||||
This is used to guard against database upgrades being performed multiple times on the same database.
| |||||||||||
Runs all upgrade prerequisites.
| |||||||||||
Once the upgrade is complete, we'll need to set the new database build number in the database.
| |||||||||||
Once all upgrade tasks have been completed without error, make sure the build number stored in the applications main configuration file and database now matches
the build number of this version of the release.
| |||||||||||
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
| |||||||||||
From interface
com.atlassian.confluence.upgrade.UpgradeManager
|
This is the build number of the current version that the user is running under. This version is stored in their confluence home confluence.cfg.xml file
This is the build number of the data in the database. If the version of the database data can not be
determined, this method should return the same value as getConfiguredBuildNumber()
.
The is the build number of the new version of Confluence being upgraded to. This number can be found in the default.properties of the new expanded WAR
This is used to guard against database upgrades being performed multiple times on the same database. By default, assume a non-clustered setup and allow database upgrades.
UpgradeException |
---|
Runs all upgrade prerequisites.
Once the upgrade is complete, we'll need to set the new database build number in the database.
Exception |
---|
Once all upgrade tasks have been completed without error, make sure the build number stored in the applications main configuration file and database now matches the build number of this version of the release.
Exception |
---|