ProfileManager will be converted into a proxy bean that gets the actual bean id to use as the implementation from sakai.properties like so:
The value above is the default. Thus, the actual implementation of ProfileManager has been converted into LegacyProfileManager. The profile tool uses this legacy bean and is unaffected.
This allows different implementations to be plugged in via sakai.properties, eg a Profile2 impl of the ProfileManagerso that Roster and other tools can get their data from Profile2 preferentially, if desired, and without affecting any other tools.
This will also allow both Profile and Profile2 to run side by side