Excluding nested transitive dependency in maven

Question

My project depends on jparsec, which depends on cglib, which depends on asm. My project also directly depends on asm, but a newer version than the one cglib depends on:

It seems I cannot exclude asm from my jparsec dependency. When I attempt to exclude it with Eclipse, it makes no change to my pom. If I manually exlude it, it has no effect.

Is my only option here to exclude cglib from jparsec and then to manually add a dependency on cglib with asm excluded? This seems a bit convoluted to me, but it does work.

Answer 1

I would have expected that if you put asm before jparsec in your POM, no exclusion would be required. The Maven "nearest definition" behaviour would kick in to ensure only 4.1 is used.

Answer 2

As per my comment, you have 2 options to solve this issue:

1. The one that you suggested, e.g. exclude cglib from jparsec and add cglib with asm excluded.
2. Locate your asm dependency above the jparsec dependency.