|
|
|
This can be fixed by providing
maven.announcement.lenient=true But, still, Why is breaking compatibility acceptable?
Why not default it to true and allow those that want the feature to set it to false? I personally don't see the reasoning. Got an email discussion thread for me to read up on the history? This was done before I joined the Maven team, I don't know the history. I was not aware of a compatibility problem though, Felipe's comments at
Confirming that a build succeeds with m1.0.2 (announcement-plugin-1.3), but fails with 11rc1 if lenient is not set.
I don't feel like fixing this for m11-final though, I'd just document it as a compat problem... |
|||||||||||||||||||||||||||||||||||||||||||||||||
MPANNOUNCEMENT-19.