Removing a managed dependency that has configuration beyond just GAV

[crankydillo]

• Retain dependencyManagement entries with exclusions #4387 was an attempt at addressing a related concept.

I can understand there could be some nuance to this. I'd be cautious on removing a dependency if it had any configuration, not just exclusions.

An easy option is to just make the recipe configurable: e.g.:

1. always remove (behavior before Retain dependencyManagement entries with exclusions #4387)
2. remove only the version Replace the 'local' managed dependency's version with the new version from the parent.
3. don't remove (current behavior)

[crankydillo]

I think I suggested 'just remove version' last time, but I don't think that works with dependency management (should test, but that's what I recall:)

[crankydillo]

@timtebeek I'm really thinking that what we want is 'sync local managed version with parent'. I understand there are trade-offs. No recipe like that already exists, does it?

[timtebeek]

hi @crankydillo ; thanks for having another look at this one! I think indeed option 2 might be best; I'm not aware of any such recipe or visitor right now, but haven't extensively looked.