Hi, coming from maven world you are actually able to control classpath order as of version 2.0.9 maven uses pom order for classpath so you can manipulate it freely and it has proven very useful in the past for us. From what I read (and I may be wrong) Gradle doesn’t give any guarantees about the c…

[image] vehovmar: Can someone point me to the right direction how to implement similar behavior as Maven provides? Meaning preserves the ordering inside dependencies block. Even if it means writing a plugin or whatever. This isn’t necessary. The order inside the dependencies { } block is pres…

You are kind of right. Dependency ordering is preserved, but for example all compile dependencies will be before testCompile dependencies no matter of how you order them.

Depending on the nature of your conflict you could also exclude the dependency from ‘testCompile’ rather than force the correct one higher on the classpath.

Yes basically that is what we eventually… prepending specific dependencies as discussed in other topics on the forum.

Hi there, I have noticed that if you add the dependency programmatically, i.e. project.dependencies.add(‘compile’, ‘my.group:my-artifact’) order is not preserved. Not only that but although it evaluates to the same thing across invocations, it’s not the same on different machines. Do you have any …

Have you considered fixing your classpath so that there’s one of each resource/class? You could identify the duplicates via: task findDuplicates { doLast { Map<String, List<File>> pathMap = [:] configurations.runtime.each { file -> FileTree tree = file.directory ? fileTree…

That is difficult if you are using third-party commercial libraries which contain older implementations of (say) commons-lang classes. It’s awkward, but it happens.

You could remove the classes from the offending jar as part of your build. configurations { jarCleanup { transitive = false } } dependencies { jarCleanup 'foo:dirty-dependency:1.0' compile files({ tasks['cleanupJar'] }) } task cleanupJar(type: Jar) { archiveBaseName = 'clean-dependen…

[image] mark_vieira: This isn’t necessary. The order inside the dependencies { } block is preserved. I wish to find some evidence of this in the API, but I can’t find anything. Traversing the dependency tree is done using sets, not lists. For example, we start with: task printDeps { doLa…

Deterministic ordering of dependencies on the classpath

Help/Discuss

bradmac-ats (Brad Mace) June 29, 2019, 1:23am 7

This doesn’t seem to be true? If there’s any relationship between their order in the build file and their order in the classpath, I can’t work out what it is.

Topic		Replies	Views
Classpath ordering, again Old Forum Archive	9	5727	December 31, 2014
Yet another classpath ordering question Help/Discuss	1	1095	August 9, 2020
Order of resolved dependencies Old Forum Archive	2	1021	December 11, 2012
Compile classpath order Old Forum Archive	5	1966	February 10, 2015
Eclipse classpath ordering - project dependency always at the bottom of dependencies Help/Discuss	16	7059	February 1, 2017

Deterministic ordering of dependencies on the classpath

Related topics