Class SynchronyPidFileRemovalUpgradeTask
java.lang.Object
com.atlassian.confluence.upgrade.AbstractUpgradeTask
com.atlassian.confluence.upgrade.upgradetask.SynchronyPidFileRemovalUpgradeTask
- All Implemented Interfaces:
- BackupSupport,- UpgradeTask,- UpgradeTaskInfo,- org.springframework.beans.factory.Aware,- org.springframework.beans.factory.BeanNameAware
Deletes synchrony.pid file as it's not used by Confluence anymore.
- Since:
- 7.14.0
- 
Field SummaryFields inherited from interface com.atlassian.confluence.upgrade.UpgradeTasklog
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionbooleanReturns true if a new export can't be imported in an older instance.voidPerform the upgrade.booleanReturns true if an older Space can't be imported in a new instance without running this task.Methods inherited from class com.atlassian.confluence.upgrade.AbstractUpgradeTaskaddAllErrors, addError, addError, getConstraint, getErrors, getName, getShortDescription, isDatabaseUpgrade, setBeanName, setBuildNumber, validate
- 
Constructor Details- 
SynchronyPidFileRemovalUpgradeTaskpublic SynchronyPidFileRemovalUpgradeTask()
 
- 
- 
Method Details- 
runOnSpaceImportpublic boolean runOnSpaceImport()Description copied from interface:BackupSupportReturns true if an older Space can't be imported in a new instance without running this task. For example:- A task updating macro names in the BodyContent table would be blocking.
- Tasks which updates data related to the space would be blocking.
- A task upgrading the user table wouldn't be blocking.
- Adding a mandatory column on space-related content breaks space import
 Note that tasks don't run on space import yet, so we just reject the import in this case. 
- 
breaksBackwardCompatibilitypublic boolean breaksBackwardCompatibility()Description copied from interface:BackupSupportReturns true if a new export can't be imported in an older instance.Breaking compatibility means a snapshot of the new version will not work at all with the previous version. For example: - A destructive operation (Some data is replaced by another) breaks backwards compatibility
- Adding a optional column does NOT break backwards compatibility
- Data is copied to another column doesn't breaks backwards compatibility
- A build number incrementation doesn't breaks backwards compatibility
 
- 
getBuildNumber- Specified by:
- getBuildNumberin interface- UpgradeTaskInfo
- Overrides:
- getBuildNumberin class- AbstractUpgradeTask
- Returns:
- The build number that this upgrade is applicable to
 
- 
doUpgradeDescription copied from interface:UpgradeTaskPerform the upgrade.- Throws:
- Exception
 
 
-