Hi Jessie,
You inspired me to do quick search for "outputDirectory" in all the POMs and I
found this little bugger in all the projects' common parent pom:
<reporting>
<outputDirectory />
[ … ]
</reporting>
Not sure what purpose it served - but once removed, the projects behave as
expected in Maven 3 :).
Thanks for the help!
- hugi
// Hugi Thordarson
// http://hugi.karlmenn.is/
On 31.7.2011, at 14:38, Jesse Farinacci wrote:
> Greetings,
>
> On Sun, Jul 31, 2011 at 10:28 AM, Hugi Thordarson <[email protected]> wrote:
>> I just upgraded to Maven 3. Now, when I run "mvn clean" on a multi-module
>> project it will delete each module entirely, rather than just the target
>> directories contained within each module directory (which is how it used to
>> work in Maven 2).
>> Anyone have any idea what I might be doing wrong here?
>
> Maven output or it didn't happen. I simply do not believe this is what
> is happening unless you've somehow attached to clean phase an antrun
> execution to delete all your modules.. or you've put them under
> build.outputDirectory.
>
> -Jesse
>
> --
> There are 10 types of people in this world, those
> that can read binary and those that can not.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
