Move the optional package (extension) directory outside of the JRE (lib/ext) so the installed extensions can be used with different versions of the JRE and possibly by different people. Also possibly have a variable that users can set to specify the extension directory.

The permission for the extension directory (lib/ext) is set in the default (lib/security) java.policy file.

grant codeBase "file:${java.home}/lib/ext/*" {
permission java.security.AllPermission;
};

Security issues will have to be thought of and worked out.

Because Native and Java install type programs install the extension to the JRE/lib/ext directory we may still have to keep and support the JRE/lib/ext directory for backward compatibility reasons. When this change is made the extension developer may have to change their install program to install the extension to the new default extension directory, or give the user a choice on where to install the extension, or we could move the installed extension from the old <jre>/lib/ext directory to the new extension directory after the extension has been installed.

The Raw type of install should not be a problem.

There might be other problems with doing this because some optional packages may install other support type files in other places in the JRE besides the extension directory lib/ext. Or the optional package may need to be installed in the JRE to work properly.

Document changes to the deploying optional packages document will need to be made to explain this change.

All of the above issues and maybe more will need to be worked out in more detail at a later time.