Eclipse plugin does not respect the classpath order in all cases


I’m building a multiproject where multiple versions of libraries have to coexist. The command line gradle build works flawlessly, but this is not true for Eclipse. It seems like ‘project’ dependencies are moved to the top of the classpath and the remaining library dependencies are left in the original order. If I manually reorder the items everything starts to work again with the exception that exclusions on projects are not respected.

I found that org.gradle.plugins.ide.eclipse.model.internal.ClasspathFactory creates the classpath just the way I described. This is very problematic as the order of entries on the classpath is crucial. Is there any way to restore the original order that is present on the command line?

I’d highly appreciate any help.

Thank you, Andras