When one uses java_ark provider in own cookbook to install several javas on a machine, there are 2 issues:

1. The provider removes alternatives configuration before installing alternative for bin cmd. So, if one has another java installed manually, or install several ones using own cookbook, only latest appear in alternatives. Another one issue here is, the latest installed one becomes active in spite of priority and while installation is in progress, the one is being installed is active.
2. [COOK-1114] Fixed "no method exists? for the Chef::Resource::File class" error in the "openjdk" recipe #1 can be mitigated by setting default attribute to false. However, if value of 'default' attribute for a resource is false, it forces adding '_alt' suffix for directory name and this cannot be controlled. Therefore, if one decides to switch java installation from one to another, it will install two javas again. So it's nice to have a switch to control this behavior.
3. If priority of alternative gets changed, and the provider installs already existing alternative (but with another prio), the alternative switches to manual mode if it was auto.

This change corrects all these issues. But all defaults are set that way, so original behavior remains.