Components classloader is dependent on filesystem ordering and so not predictable

The building of the classloader for a component is dependent on the order that files are returned from the filesystem. This can lead to unpredictable deployments where one node in a cluster will load different classes to another node.

Locally we had this issue where the same class was deployed in 2 different JARs and different nodes in our cluster loaded different classes and on some nodes we had the tool fail.

On linux ext4 File.listFiles() returns the files unsorted, in the order they are stored in the directory.

On HFS+ on my Mac I would always get the files back alphabetically.