We separate all code scanning activities from *builds*. Our builds are
designed to fail fast by just doing the compile, unit test and
packaging. We run a secondary process, that we don't feel has the same
time constraint, to perform documentation and analysis. 


________________________________

Curt Yanko | Continuous Integration Services
Making IT Happen, one build at a time

-----Original Message-----
From: Thomas Scheffler [mailto:[email protected]] 
Sent: Tuesday, September 28, 2010 7:11 AM
To: [email protected]
Subject: findbugs and javadoc trigger compile lifecycle

Hi,

I use findbugs and javadoc as reporting plugins. Both trigger the
compile lifecycle when running "mvn site". How do I disable this trigger
or at least how to I have only ONE compile lifecycle as this is a real
long running phase.
Normally I run "mvn deploy" before "mvn site" so that all sources are
already compiled at that stage.

For the records the current plugin definition:

  <reporting>
    <plugins>
      <plugin>
        <artifactId>maven-javadoc-plugin</artifactId>
        <version>2.5</version>
      </plugin>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>findbugs-maven-plugin</artifactId>
        <version>2.3.1</version>
        <configuration>
          <xmlOutput>true</xmlOutput>
          <findbugsXmlOutput>true</findbugsXmlOutput>
        </configuration>
      </plugin>
    </plugins>
  </reporting>

Thanks for your support.

Regards

Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to