Details
-
Type:
Bug
-
Status:
Tested
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Gliffy Plugin for Confluence 2.0.1
-
Fix Version/s: Gliffy Plugin for Confluence 2.0.2
-
Component/s: None
-
Security Level: Anyone may view
-
Labels:None
-
Iteration:1
Description
Reported by Charles @ Atlassian:
Firstly, in upgrading our internal Atlassian Confluence wiki to a 3.1 milestone we discovered that the gliffy plugin relies on a couple of classes that have been deprecated for a couple of years and are scheduled to be removed in 3.1.
The classes in question are:
bucket.container.ContainerContext
bucket.container.ContainerManager
These classes have been deprecated in favour of:
com.atlassian.spring.container.ContainerContext
com.atlassian.spring.container.ContainerManager.
Replacing references to the 'bucket' classes with their 'com.atlassian.spring' alternatives should be pretty simple while still maintaining compatibility back as far as Confluence 2.3. I'd suggest grabbing a copy of the Confluence Milestone 2 release (due out in the next week or two) for advance testing.
I've done a bulk find and replace about 50 references to bucket.container.ContainerManager. I can't find any references to bucket.container.ContainerContext.
A quick test hasn't shown any problems in Confluence 3.0. Will need to test against the milestone build once it comes out (or give Atlassian a SNAPSHOT build to test internally).