[MNG-7020] Remove Maven 2 WagonExcluder backward compat code

[michael-o]

No description provided.

[rfscholte]

Based on just the code this looks good and based on the comment this should be safe to do. I don't know where to expect any impact, if any.

[michael-o]

@rfscholte Since you approved this, can I go on and merge?

[rfscholte]

IIRC this triggered a new issue. I'll remove my approval and need to have another look at it.

[michael-o]

Sure...

[cstamas]

Unsure what to say here...

This was in place for Maven2 plugins (running in Maven3). Hopefully today they will break with Maven4, so WagonExcluder is really not needed as plugin will not even execute. Still, IMO we'd need some safety "thing" maybe simply reject plugins declaring dependency on Maven artifact(s) having version 2.x? Just to be on safe side? (like prerequisite, but other way around)

[rfscholte]

@cstamas @michael-o I thought we also worked on that "require maven-plugin-api version", but can't find the ticket. For me that must be implemented first before accepting this PR.

[michael-o]

@cstamas @michael-o I thought we also worked on that "require maven-plugin-api version", but can't find the ticket. For me that must be implemented first before accepting this PR.

That is true and that is why I have not yet merged it.

[slachiewicz]

That was MNG-7122 184db56

[michael-o]

@rfscholte Can you reassess please?

[mthmulders]

All integration tests are failing - could it be it's an outdated version of the IT's? Other than that, it looks fine to me.

[michael-o]

Let me check...

[michael-o]

@mthmulders I have rebased the branch, I guess the ITs should pass. Let's wait.