Dear sir,
According to specifications, I don't think you can be guaranteed any
load-order of .jar files in this way.
Anyway, if classes are really the same, the jar load order shouldn't
matter... And I wouldn't recommend under any circumstances to use
different classes - with same package and classnames... Most likely,
you'll end up with with a marshalling error down the road (when
different classloaders on fx. client/server loads from a.jar and b.jar
- and try to process objects passed from each other).
As you're probably aware of - just remember to make sure that classes
using each other through static initializers are all contained in the
same .jar . That's easier than trying to make sure that .jar's are
loaded in any particular order.
Hope to have been of service! Best of luck.