tree 1728593cb3706cc4be4d4e7a90f50692757aff39
parent 367b2101f4c49e6b807f16260a78fdb1da02f608
author Tamas Cservenak <tamas@cservenak.net> 1684521237 +0200
committer GitHub <noreply@github.com> 1684521237 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkZ8EVCRBK7hj4Ov3rIwAA4d8IAIKhZL3Y4EzIy8DuFVE5kVGa
 B3UDM0djaVngUpzdCqhdW53u4HDFU91Ufhld+Q/gJKamzVOml1LlfsWfEyvXi5D9
 C2RceKS93TM54d6IprykXfoECLoj16qcg7WzkKQwdyU0auSdUwtff7SDulwLrvV3
 7YYPvlLGZC+ya79WV1tR+CLleT+84V5azFJ2+aro6LTCl3owEPBjWzOx0iYKTxn5
 lqVW2cBb5S+cVl9RYWeVng3oaGnl8/AmCIjMlWFFZOXBU+bXLQGlYHPEdrobvPwu
 jSR+fkkkqAap9bg0qK2UrtvLbhY6IF/dS63rhF7YYF82feuNU/85bS1C8bVe98w=
 =OQlt
 -----END PGP SIGNATURE-----
 

[MNG-7788] Fix for IT MavenITmng6562WarnDefaultBindings (#261)

The MavenITmng6562WarnDefaultBindings IT tests new Maven4 feature "fail on severity" (for WARN level).

The stub core plugin maven-resources-plugin depends on maven-compat, and it emits plugin validation warning.

BEFORE MNG-7788 was merged, the warnings were logged AFTER build summary and was not picked up by "fail on severity".

AFTER MNG-7788 merged, it causes that warnings breaks the build, as "fail on severity" is set to WARN level.

Fix:
The stub maven-resources-plugin does NOT need to depend on maven-compat, what it really needs is maven-core (for MavenProject).