Discover conflicts with different group / names - some kind of mapping?


(Wujek Srujek) #1

HI. I have the following case: I am using 2 libraries (groovy 2.0.0 which uses org.ow2.asm:asm:4.0 and cglib:cglib:2.2.2, which uses asm:asm:3.1). Additionally, I set the build so that it fails for any library conflicts. Of course, here a conflict is not detected, as the group is different. Do you think it would be possible to add some king of a ‘module mapping’ to gradle, so that it could also discover such conflicts?


(Peter Niederwieser) #2

Yes, I think this would make sense. Even better if Gradle already came with a default list of duplicates (or would fetch a duplicate list from an external source).