It is always a big investment, especially when migrated from Maven 2 to
Maven 3.0 API.
For me it make sense to make minimum viable migration steps, and therefore
migrate the plugins with major versions only.
In this case it would be a migration with Java version 8.0 and Maven API
4.0 or 5.0.
On Fr
Even though we release the Maven APIs together with Maven Core (with the same
version), for plugins there are close to no changes.
The biggest changes of Maven APIs are from 2.2.1 to 3.0 and 3.0.5 to 3.1.0
With this in mind, having almost all plugins depending on 3.0, it makes sense
to start movi
Hi,
Community support is always an interesting question as there is no support
contract to define what "support" means ;)
IMO, the community does at least support the latest release. Then if some
community members can work on supporting older ones, that's good, but IMO
it doesn't have to be the pr
Seems to me that fixes are never back-ported, meaning only the latest
version of Maven is really supported. That being said, care also seems to
be taken to not make changes in plugins which break older versions of
Maven. I think you ask an important question, because trying to keep
plugins working
We're coming up on the ten year anniversary of Maven 3.0.
Maven 3.2.5 was, I think, the first to support Java 6.
3.3.9 is five years old.
Some of our documentation still references Maven 2 and Maven 3 as if
the difference matters. It does, but we can mostly just assume Maven
3, I think, and igno
