Re: [m2] changing the output directory in a forked and custom lifecycle

[Brett Porter]

The expected behaviour is that the output directory is changed for the 
instrument goal only. If you want to change the project.build.directory 
value itself, the instrument goal will need to do that.

There is an integration test checking this functionality works - if 
you've found a case where it doesn't behave as described, please file it.

Thanks,
Brett

Vincent Massol wrote:

Hi,

I am using the new @execute tag with a custom lifecycle.xml:

<lifecycles>
 <lifecycle>
   <id>clover</id>
   <phases>
     <phase>
       <id>generate-sources</id>
       <executions>
         <execution>
           <configuration>
<outputDirectory>${project.build.directory}/clover</outputDirectory>
           </configuration>
           <goals>
             <goal>instrument</goal>
           </goals>
         </execution>
       </executions>
     </phase>
   </phases>
 </lifecycle>
</lifecycles>

I was expecting that this would modify the project.build.directory value so
that all goals called thereafter and using ${project.build.directory} would
use the new value. But it's not happening.

Can anyone tell me what is the expected behavior?

Thanks
-Vincent


---------------------------------------------------------------------
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]