EOL.Wiki EOL.Wiki
← ← Back to all products

Apache Maven

Active
Tools & Monitoring Latest Version: 3.9.12 Latest Release: Dec 13, 2025

Apache Maven is a build automation and project management tool primarily for Java projects.

Versions

10

Latest Version

3.9.12

Active Support

1

EOL

9

Lifecycle Timeline

Today
3.9
3.9
3.8
3.8
3.6
3.6
3.5
3.5
3.3
3.3
3.2
3.2
3.1
3.1
3.0
3.0
2
2
1
1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.9Jan 31, 2023-No3.9.12No
Active
3.8Mar 30, 2021-Jun 14, 20253.8.9No
EOL
3.6Oct 24, 2018-Mar 30, 20213.6.3No
EOL
3.5Apr 3, 2017-Oct 24, 20183.5.4No
EOL
3.3Mar 13, 2015-Apr 3, 20173.3.9No
EOL
3.2Feb 14, 2014-Mar 13, 20153.2.5No
EOL
3.1Jun 28, 2013-Feb 14, 20143.1.1No
EOL
3.0Oct 4, 2010-Jun 28, 20133.0.5No
EOL
2May 7, 2006-Feb 18, 20142.2.1No
EOL
1Jul 13, 2004-Feb 18, 20141.1No
EOL

Frequently Asked Questions

Which versions of Apache Maven have reached end of life?
The following Apache Maven versions have reached end of life and no longer receive security updates: 3.8, 3.6, 3.5, 3.3, 3.2, 3.1, 3.0, 2 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Apache Maven 3.8?
Apache Maven 3.8 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache Maven?
The latest version of Apache Maven is 3.9.12, released in the 3.9 release cycle.
How many versions of Apache Maven are currently supported?
Apache Maven currently has 1 actively supported version(s): 3.9.
When does Apache Maven 3.9 reach end of life?
Apache Maven 3.9 does not have a specific end-of-life date announced yet.
What should I do when Apache Maven reaches end of life?
When a Apache Maven version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.