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