On Sun, 8 Oct 2023 at 22:53, sebb <seb...@gmail.com> wrote: > > > > On Oct 8, 2023, at 7:11 AM, sebb <seb...@gmail.com> wrote: > > > > > > There are currently lots of variations of the defaultGoal in different > > > components. > > > > > > It may be sensible to establish a standard setting which components > > > should adopt (unless there is a good reason to do otherwise). > > > > > > If so, what should that be, and where does it get documented? > > > > > > Personally, I don't think install should ever be a default goal as it > > > changes the environment outside the component. > > > > > > Main goals seen: > > > clean > > > install > > > package > > > site > > > test > > > verify > > > > > > Other goals seen: > > > apache-rat:check > > > checkstyle:check > > > clirr:check > > > findbugs:check > > > japicmp:cmp > > > javadoc:javadoc > > > pmd:check > > > pmd:cpd-check > > > spotbugs:check
Note that some poms will be configured to use executions to bind goals to lifecycle phases. So the default goal may only be 'clean verify' but many plugins will be executed. For example the commons-parent pom runs apache-rat-plugin in the validate phase making this explicit goal redundant in all our projects; the multi-module RNG component uses 'clean verify javadoc:javadoc' but executes PMD, SpotBugs and Checkstyle in executions bound to the verify phase. There are also some plugins that have executions bound to verify but activated by the presence of a file, for example RevAPI/JApiCmp for modules building a jar; these can be disabled by lack of a file for modules with a non-jar packaging. I think making the default goal run verify is appropriate as this is where many validation plugins are conventionally configured to run. It allows a quicker build with 'mvn test' and a full check with 'mvn'. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
