On Wed, Jan 20, 2016 at 6:03 PM, Jesse Glick <[email protected]> wrote:
> On Wed, Jan 20, 2016 at 4:22 AM, Stephen Connolly > <[email protected]> wrote: > >> I would suggest `<preparationGoals>javadoc:javadoc clean > >> install</preparationGoals>` > > > > -1 as that may give a false fail on a clean checkout where the javadoc > > plugin references generated classes > > Possibly. What I do in `workflow-plugin`, which has served me well, is > to just include `javadoc:javadoc` in a profile activated when not > `skipTests`. That ensures that all “full builds” including CI verify > the absence of Javadoc errors, so you do not get a nasty surprise on > release day. Routine developer builds—where you are just trying to get > artifacts created so you can `hpi:run` etc.—do not incur the expense. > > That has been included, but independently of findbugs: https://github.com/andresrc/plugin-pom/blob/03f2c716f68f9142d3b8fbb14fd9b8af3d154b0a/pom.xml#L804-L827 > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr05ksqCt7UJmKd4FWnZUMtNAXASO6ESShWt-3hmqAYXUg%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Regards, Andres Rodriguez www.cloudbees.com -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAM9%3DZ%2B70wf7TfK1j1dYvQ0p1FoYNCyXAb24d8dVvo8qC92VNjw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
