NOTE: This is an ALPHA release. There is the potential that features may be
added/removed between this release and the first GA release in the 3.5.x
Please consult the Known Issues section below before use
You can download the appropriate sources, etc. from the archives section on
the download page as Maven 3.3.9 is still the recommended GA release
The following issues were identified during release testing of this ALPHA
release but have not been deemed as release blockers:
MNG-6177 The --file and -f option to specify a pom.xml to use
does not work if the path includes characters that need quoting such as
whitespace or &.
MNG-6115 If Maven is installed in a writable location, every build will
create a new lib/ext/jansi-.... file.
Why not Maven 3.4.0?
After Maven 3.3.9 was released, the Eclipse Aether project was retired and
the code base was migrated to the Apache Maven project.
The original goal for the 3.4.0 release was to replace Aether with the
exact same code after migration to the Apache Maven project and then
proceed with bug fixes to the resolver code as well as other areas of Maven.
The migration of the code between the two foundations took longer than
expected and as a result there were other changes committed to Maven core
that were outside the scope of intent for 3.4.0.
In order to refocus on the original intent for 3.4.0, the decision was
taken to revert the Maven core history to the point of the 3.3.9 release
and merge in the desired changes one at a time.
Because there had been a lot of communication about different features
being delivered and bugs fixed in Maven 3.4.0 and the new history may not
contain them in the first release, the decision was taken to forever burn
the 3.4.x release line.
so far so good. Now let us assume we have the following two versions:
What would you expect which version is newer than the other or the older one?
I suppose you would say: 126.96.36.199.1 is older than 188.8.131.52 or with other
words: 184.108.40.206 is newer than 220.127.116.11.1 or to express it in a more
18.104.22.168.1 < 22.214.171.124
Or another example:
So I assume that you have expected that Maven 2 should have handled that like this:
1.0alpha10 > 1.0alpha2
Unfortunately Maven 2 had handled them different because the previous versions
did not follow the above pattern which results into string based comparison of
the versions and finally into the following result:
126.96.36.199.1 > 188.8.131.52
1.0alpha10 < 1.0alpha2
which is obviously not the result you have expected.
Starting with Maven 3 (released 2010!) the version comparison has been changed
but unfortunately the above myth keeps tenaciously.
So the first thing is that you can use as many digits as you like and separate them
by dots. This means the following versions are valid:
Regarding the above list which version is mathematically greater,
greater or equal, less than, less or equal than the other?
So what about things like 1.6.0-RC1 ? Let us assume we have the following
So how does the comparison result look like? If you think a little you might
already know the solution. The 1.6.0-RC1 is of course older than 1.6.0 or
1.6.0-RC1 < 1.6.0
This is because a release candidate is created before the final 1.6.0
release. So other things could be concluded out of the above like this:
which is this way based on the assumption made above. Milestones are before the
final releases. So of course you can conclude ordering of milestones like this:
1.6.0-m1 < 1.6.0-m4
1.6.0-m4 < 1.6.0-m10
The above is also valid for the cases where we separate the milestone via a
dot instead of a dash.
1.6.0.m1 < 1.6.0.m4
1.6.0.m4 < 1.6.0.m10
You can do things like the following if you like:
1.6.0-m184.108.40.206 < 1.6.0-m220.127.116.11
So now we come to an important thing, if we compare the following
two versions 1.6.0-m1 with 1.6.0.m1. On the first glance
you might think those two versions are equal because they describe
a milestone with the same version 1.6.0. The result of the comparison
in Maven is different:
1.6.0-m1 < 1.6.0.m1
This means in consequence that a part which is separated via - is less important
than a part wich is separated via ., or the part which is separated via .
has precedence over the part which is separated via -.
We have only considered releases yet. So now let us take a look at SNAPSHOTs.
So let us try to see which version is before the other one in case of such
version 1.6.0-SNASPHOT and 1.6.0.m1? So you might already know the result.
The SNAPSHOT version is before the other one 1.6.0.m1 cause a SNAPSHOT means
there has no release before of 1.6.0.
You can add the -SNAPSHOT part to each of the above examples but the results
will keep the same.
If you like to experiment with some of the above examples or check your ideas
you can simply use your existing(?) Maven installation for this. Starting with
Maven 3.2.5 there is a command line interface which can
show you the comparision results for versions given on the command line like
This API is concerned with firing a Maven build in a new JVM. It accomplishes
its task by building up a conventional Maven command line from options given in
the current request, along with those global options specified in the invoker
itself. Once it has the command line, the invoker will execute it, and capture
the resulting exit code or any exception thrown to signal a failure to execute.
Input/output control can be specified using an InputStream and up to two
You can download the appropriate sources etc. from the