cstamas commented on PR #765: URL: https://github.com/apache/maven/pull/765#issuecomment-1182977992
Well, just as you say, Maven3 has no API, hence, really no "easy" way to detect this "breakage" (as 3.x plugin could still declare dependency on maven-plugin-api:3.1 AND maven-compat:3.1 -- we may extend this check in this PR for that btw!), but one thing for sure: IF they use maven-plugin-api:2.x we KNOW it is either ancient plugin, or... If anyone MUST produce plugin that works with Maven2 AND Maven3, they should be aware they are missing the Maven4 train, and hence, I can assume they will stick with 3.8.6 for Maven3 (and who knows what version of Maven2) and it will not nag them. But, I bet we talk about minority here, and I guess as they do this, they already know what they are doing anyway. Re metadata: If we start adding metadata, propagation of that metadata will take eons thru ecosystem (with 2.x plugins being still in use), so see my "slow rant" for that. IMHO instead of some "lab" (scalpel) approach, yes, this is more like "root it out" (axe or hoe), just make it gone, kill it in root. Hence, it is completely safe to assume if plugin: * depends on plugin-api less than 3.1 * OR depends on maven-compat whatever 3.x version (to be added) * => we deal with ancient plugin -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
