On Mon, Jan 19, 2015 at 1:24 AM, Kevin Burton <[email protected]> wrote:
> The main situation I see is when the artifact and group ID differ … > > so an older version of jdom used just jdom and the newer version used > org.jdom and then I ended up with both :) > > Kevin, Specific to jdom, I don't believe any duplicate class checking will help you here as the classes for JDOM 1.x are in different packages vs. JDOM 2.x. The upgrade path from 1.x to 2.x _requires_ code modification[1], though I believe both versions can coexist (probably the reason for the different artifact coordinates). The most help I believe maven can provide you here is with exclusions and/or the bannedDependencies[2] rule of the enforcer plugin. HTH, Doug [1] https://github.com/hunterhacker/jdom/wiki/JDOM2-Migration-Issues [2] http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html
