RE: [m2] Modifying project.build.sourceDirectory and executions

2006-01-13 Thread Vincent Massol
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: vendredi 13 janvier 2006 00:00 > To: Maven Developers List > Subject: Re: [m2] Modifying project.build.sourceDirectory and executions > > This is because the part of clover that runs is fo

Re: [m2] Modifying project.build.sourceDirectory and executions

2006-01-12 Thread Brett Porter
This is because the part of clover that runs is forked, and the project is cloned then reset when it returns. This is by design, so forked lifecycles don't polllute the original. The final clover goal that cause the fork has access to ${executedProject}, and can pump settings back into the main pro