Compare this original version: [ERROR] Failed to execute goal on project emerge-monolithic-services: Could not resolve dependencies for project nz.co.company.emerge:emerge-monolithic-services:jar:40.166-SNAPSHOT: Failed to collect dependencies for nz.co.company.emerge:emerge-monolithic-services:jar:40.166-SNAPSHOT: Could not resolve version conflict among [nz.co.company.emerge:emerge-services:jar:[8.563,9) -> nz.co.company.ristretto:ristretto-aaa-api:jar:[5.16,6), nz.co.company.emerge:emerge-services:jar:[8.563,9) -> nz.co.company.milo:emerge-task-services-v1:jar:[1.63,2) -> nz.co.company.ristretto:ristretto-aaa-api:jar:[5.16,6), nz.co.company.ristretto.aaa:ristretto-aaa-client:jar:[4.6,5) -> nz.co.company.ristretto:ristretto-aaa-api:jar:[5.16,6), nz.co.company.emerge.integration:emerge-digital-assets-axle-v1:jar:[1.17,2) -> nz.co.company.ristretto:ristretto-aaa-api:jar:[3.8,4)] -> [Help 1]
With this manually formatted version: [ERROR] Failed to execute goal on project emerge-monolithic-services: Could not resolve dependencies for project nz.co.company.emerge:emerge-monolithic-services:jar:40.166-SNAPSHOT: Failed to collect dependencies for nz.co.company.emerge:emerge-monolithic-services:jar:40.166-SNAPSHOT: Could not resolve version conflict among [ nz.co.company.emerge:emerge-services:jar:[8.563,9) -> nz.co.company.ristretto:ristretto-aaa-api:jar:[5.16,6) nz.co.company.emerge:emerge-services:jar:[8.563,9) -> nz.co.company.milo:emerge-task-services-v1:jar:[1.63,2) -> nz.co.company.ristretto:ristretto-aaa-api:jar:[5.16,6) nz.co.company.ristretto.aaa:ristretto-aaa-client:jar:[4.6,5) -> nz.co.company.ristretto:ristretto-aaa-api:jar:[5.16,6) nz.co.company.emerge.integration:emerge-digital-assets-axle-v1:jar:[1.17,2) -> nz.co.company.ristretto:ristretto-aaa-api:jar:[3.8,4) ] -> [Help 1] It's very hard to scan through the wrapped one line version looking for the actual offending things, and tracing back their resolution paths in the real version. In my hacked version you can easily scan each line and settle on the end seeing exactly what's wrong in a fraction of a second. If there's some agreement on this, I'd be happy to submit a patch. I've not looked at where the code lives, but it's quite horrible to use right now. Regards, Fred.
