Attaching plugins to lifecycles

[Thomas Leonard <ta...@it-innovation.soton.ac.uk>]

Hi all,

I've got a largish multi-project setup (74 projects) with various extras
attached to the build lifecycle (clover coverage reporting, deploying
wars to tomcat, verifying JSP, check-style, etc). These are enabled
using profiles.

The trouble is, these extensions tend to interfere with each other. For
example:

- Checkstyle checks that each file has our standard header. But when
used with clover, it tries to check the instrumented clover source files
and fails (because clover adds its own header text).

- When deploying a war with clover, two wars get built and deployed to
tomcat (one instrumented and one not). I only want to deploy the
instrumented one. This is a particular problem because the wars are
pre-configured to use a particular hypersonic database, and both
versions try to use the same one!

In general, how do I specify that certain actions should only happen
during the clover part of the lifecycle, or only during the normal
lifecycle?

Thanks,


-- 
Dr Thomas Leonard
IT Innovation Centre
2 Venture Road
Southampton
Hampshire SO16 7NP

Tel: +44 0 23 8076 0834
Fax: +44 0 23 8076 0833
mailto:tal@it-innovation.soton.ac.uk
http://www.it-innovation.soton.ac.uk 

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