cstamas commented on PR #765: URL: https://github.com/apache/maven/pull/765#issuecomment-1183025980
> Sure but it is _not_ safe to say it will not work with current maven version. Best example is a plugin just adding some properties in maven project, logging some meta or generating some files from a preconfigured structure, it will run fine in most cases, so ok you have an old build of a plugin but you can't conclude much right? Last thing is "depends on" means "uses in its code" and not "has it in its dependencies" so still current impl is probably too optimistic and leads to too much false positive for end user IMHO. It all started here: https://issues.apache.org/jira/browse/MPLUGIN-372 As there was a bug in mpp that prevented setting "maven bits" (so plugin-api, maven-core, etc) to provided scope, that resulted in maven downloading (other) maven versions just to exclude them from class path. And this annoyed me a LOT, and @rfscholte also told me he got feedback from users that were confused like "am using Maven X why did Maven download Maven Y" -- well, constituent artifacts of it. Is waste from whatever aspect you look at it (bandwidth, time, energy, warming oceans). So, "old" plugin,to me it means several things: * is build against "old" plugin-api (like 2.x) * is built against maven-compat, so uses Maven2 compat layer despite is being built against Maven3 * most probably uses old tooling as well (new one emits warning during build to set proper scopes), so MOST PROBABLY will download whole maven as well. In short, IMHO we should nag users (and indirectly plugin devs as well) to keep up, especially if they want to sit on Maven 3.9 train that is taking them to Maven4. > what the user should do when it works and there is no new version because it just works? Well, I believe they do not update their operating system, Java or anything, because it also "just works". Also, if it "just works" why would they go with Maven 3.9 (why would the go the fuss to upgrade maven in the first place?). These kind of statements are full of contradictions for me, so I never considered them. > ...if we break everybody and/or make it very inconvenient to work with maven... And no, we will not break EVERYBODY, we will break (well, they will break themselves when upgrade to Maven4) those users who use Maven2 plugins, that's a huge difference: we have no resources to support compatibility across 2 major versions. Maven3 did support Maven2 plugins, just like Maven4 will support Maven3 plugins (but not Maven2). I think this is really fair expectation, but if not, stick with 3.8.6 as long as you want (the user I mean). -- 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
