Different sorting of Java CLASSPATH in install4j launcher using Scan directory option on different system environments -
we have strange behaviour calling java application using install4j launcher (install4j r5.0.11) on different environments. launcher uses scan directory option (for jar files) set classpath before starting main class. classpath logged debugging in our application.
on system 1 entries of classpath sorted ascending filename.
on sytem 2 entries sorted descending.
this leads exception on system 2, because of wrong order of 2 jars.
does "scan directory option" take account system settings (eg. sorting)?
you cannot rely on classpath sorting scan directory entries, behavior system-specific.
Comments
Post a Comment