There are two issues with the jar-reordering scheme:

1) The list needs to be updated with each release, and should be revalidated for performance benefit with each update.
   The current classlist's need updating, but we need also need to re-validate thay jar reordering is still gaining us
   a performance increase on the new HW architectures. If not, then we should rip out the jar reordering support.

2) Updating the list and revalidating the performance benefit takes manual intervention. Need to determine whether there
   is a way to automatically update the lists as part of the build process.