PMD check binding to other lifecycle phase?

[Wim Deblauwe <wi...@gmail.com>]

Hi,

I don't really understand why the PMD check is bound to the verify lifecycle
phase by default? This means that my unit tests run first and then I get an
error that there is a PMD violation. Would it not be better to do this in
the validate phase? Other candidates might be process-sources or
process-test-sources maybe if you want to check generated source files
and/or test source files also.

Anyway, how can I change this for my project to where I want it?

regards,

Wim

Re: PMD check binding to other lifecycle phase?

[Brett Porter <br...@apache.org>]

Adding the phase within the execution you have created for PMD will  
bind it to the phase that you want to use. validate is a better  
choice, but is not correct if you are generating sources that you also  
want to process.

- Brett

On 01/12/2008, at 9:29 PM, Wim Deblauwe wrote:

> Hi,
>
> I don't really understand why the PMD check is bound to the verify  
> lifecycle
> phase by default? This means that my unit tests run first and then I  
> get an
> error that there is a PMD violation. Would it not be better to do  
> this in
> the validate phase? Other candidates might be process-sources or
> process-test-sources maybe if you want to check generated source files
> and/or test source files also.
>
> Anyway, how can I change this for my project to where I want it?
>
> regards,
>
> Wim

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org