Home

Gradle resolution strategies and module metadata provide an effective way to solve the most common dependency issues, however sharing these rules between projects is cumbersome, and requires custom plugins or apply from calls. This plugin provides general purpose rule types, allowing rules to be published, versioned, shared between projects, and optionally dependency locked.

These rule types solve the most common cause of dependency issues in projects, including:

• Duplicate classes caused by changes to group or artifact ids, without renaming packages
• Duplicate classes caused by bundle dependencies, which do not conflict resolve against the 'regular' dependencies for that library
• Lack of version alignment between libraries, where version alignment is needed for compatibility
• Ensuring a minimum version of a library