maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Hoffer <>
Subject Re: Upgrading to 3.3.3
Date Mon, 14 Sep 2015 15:57:25 GMT
The reason for the Ant script is historical.  It's a very large project
that back in the day was 100% Ant.  Over time portions were migrated to
Maven, the only way to integrate with the larger Ant script is with
Today all the developer builds are pure maven but most of the CI builds
have to do more than installers, build ISO images, etc.
Unfortunately those other tasks are still Ant.

We don't have any '.mvn' folders.  Shouldn't multiModuleProjectDirectory
just default to the same folder that has the top level pom?  Not clear why
pure maven build works w/o setting multiModuleProjectDirectory but not when
using Maven-Ant-Task.

We don't call "mvn.bat" or "mvn.cmd" directly as that must be handled
by Maven-Ant-Task.
I wondered if the change from bat to cmd was the cause of the problem,
still not sure.  I did see that Maven-Ant-Task has not been updated in
quite some time, it's unfortunate if it needs to be updated for Maven 3.3.3
and not just work the same as prior versions.

Are you saying that 3.3.3 isn't going to work with Maven-Ant-Task?  If so
we will have to stay with 3.2.5 until that's updated or we can replace our
remaining Ant builds...but that isn't likely to happen soon.


On Mon, Sep 14, 2015 at 9:31 AM, Karl Heinz Marbaise <>

> Hi,
> 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:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message