maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Heinz Marbaise <>
Subject Re: Upgrading to 3.3.3
Date Mon, 14 Sep 2015 15:31:15 GMT

if you call via Ant script? Why? Special requirement ?
Are you on Windows or Linux ?

Do you call the "mvn.bat" or "mvn.cmd" file ? Do you call the file from 
the distribution ?

Apart from that the property is intended to find the root folder of a 
multi module build where the ".mvn" folder can be located...

See Release notes for more details on it...

Maven-Ant-Task has not been updated for Maven 3.3.X as far as i know...

Kind regards
Karl Heinz Marbaise

On 9/14/15 5:14 PM, David Hoffer wrote:
> We are attempting to upgrade our CI builds to use Maven 3.3.3 but are
> getting new errors with that version (3.2.5 worked).
> The error is: -Dmaven.multiModuleProjectDirectory system propery is not
> set. Check $M2_HOME environment variable and mvn script match.
> This only seems to be an issue with some of our builds, specifically the
> ones where the top level build is an Ant script that calls Maven via
> maven-ant-tasks.
> What is this new property multiModuleProjectDirectory, why was it added and
> how do I fix this? The online links on this issue seem vague and point to
> updates needed in Eclipse and IntelliJ but in my case there is no IDE just
> a CI build.
> Any help is greatly appreciated.
> -Dave

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message