Import order in referenced Libraries for unmanaged projects

Suggestion

When importing libraries in settings.json in "java.project.referencedLibraries" on a unmanaged project the order in which we import is not taken into account if there are conflicts between libraries.

Use Cases

I have a project that comes from Eclipse where the order of the entry on the .classpath is important, it will always take the first of the list in case of multiple occurence. I removed the classpath to be able to add libraries manually so it's now a unmanaged project and not an eclipse project anymore.

Examples

In my project i have many jars and some 3rd party libraries that have jars inside of them aswell, and there is some overlap between the ones i use and the ones these 3rd party libraries use, and these are not always the same version as the one i use.
So i have many errors in my project due to the fact that it takes the wrong version of the library and some function changed or does not exist anymore.

Thanks for reading me !

Start with the unmanaged-project setting in settings.json under java.project.referencedLibraries and compare its behavior with the ordering described for the Eclipse .classpath. Trace how referenced libraries are processed, then verify that the configured order determines which conflicting library version is used.