We have a multi-project build. SubprojectA has a monkey-patched-class: org.json.JSONObject (let’s not debate about how bad of an idea this is - we know sadly). SubprojectB refers to SubProjectA - and has a dependency added to a third-party library that ALSO has an org.json.JSONObject.
The problem is that when brought into Eclipse - the class in SubprojectA is being selected for compilation yet Gradle (and STS - how the code was authored) is selecting the dependency’s version of org.json.JSONObject. This causes my eclipse to complain about a compilation issue that gradle (and STS) are not experiencing.
I don’t know how to find the right file to look at the classpath - it’s not in the ‘.classpath’ file apparently. Any help here would be appreciated.
Eclipse Oxygen Release (4.7.0), BuildShip 2.1.2.v20170727-2311-s, java 1.8.0 u131 using Gradle wrapper version = ‘4.0.1’
(I didn’t find an exact match when I searched so forgive me if this is a duplicate question)