You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Alex Herbert <al...@gmail.com> on 2019/05/23 09:49:05 UTC
[rng] default maven goal
The [rng] pom does not have a default goal. Here are the default goals
in the projects I currently have checked out:
commons-codec/pom.xml: <defaultGoal>clean verify apache-rat:check
clirr:check javadoc:javadoc</defaultGoal>
commons-collections/pom.xml: <defaultGoal>clean verify
apache-rat:check clirr:check javadoc:javadoc</defaultGoal>
commons-lang/pom.xml: <defaultGoal>clean verify apache-rat:check
clirr:check checkstyle:check spotbugs:check javadoc:javadoc</defaultGoal>
commons-statistics/pom.xml: <defaultGoal>clean verify
apache-rat:check clirr:check checkstyle:check pmd:check spotbugs:check
javadoc:javadoc</defaultGoal>
commons-text/pom.xml: <defaultGoal>clean verify apache-rat:check
clirr:check checkstyle:check spotbugs:check javadoc:javadoc</defaultGoal>
These seem to match at least this:
clean verify apache-rat:check clirr:check javadoc:javadoc
Some also run:
checkstyle:check spotbugs:check
The only projects I have without a default goal are:
commons-geometry
commons-math
commons-numbers
commons-rng
I think it would be useful to run all the checks that the project is
required to pass in travis as the default goal. This can be used by a
developer as a final check before commit.
Opinions?
Is the defaultGoal a domain of the developer (as it is used above) or
should it be for an end user, e.g. where I have seen it used for 'mvn
install'.
Alex
Re: [rng] default maven goal
Posted by Gilles Sadowski <gi...@gmail.com>.
Hi.
Le jeu. 23 mai 2019 à 11:49, Alex Herbert <al...@gmail.com> a écrit :
>
> The [rng] pom does not have a default goal. Here are the default goals
> in the projects I currently have checked out:
>
> commons-codec/pom.xml: <defaultGoal>clean verify apache-rat:check
> clirr:check javadoc:javadoc</defaultGoal>
>
> commons-collections/pom.xml: <defaultGoal>clean verify
> apache-rat:check clirr:check javadoc:javadoc</defaultGoal>
>
> commons-lang/pom.xml: <defaultGoal>clean verify apache-rat:check
> clirr:check checkstyle:check spotbugs:check javadoc:javadoc</defaultGoal>
>
> commons-statistics/pom.xml: <defaultGoal>clean verify
> apache-rat:check clirr:check checkstyle:check pmd:check spotbugs:check
> javadoc:javadoc</defaultGoal>
>
> commons-text/pom.xml: <defaultGoal>clean verify apache-rat:check
> clirr:check checkstyle:check spotbugs:check javadoc:javadoc</defaultGoal>
>
> These seem to match at least this:
>
> clean verify apache-rat:check clirr:check javadoc:javadoc
>
> Some also run:
>
> checkstyle:check spotbugs:check
>
> The only projects I have without a default goal are:
>
> commons-geometry
> commons-math
> commons-numbers
> commons-rng
>
> I think it would be useful to run all the checks that the project is
> required to pass in travis as the default goal. This can be used by a
> developer as a final check before commit.
>
> Opinions?
>
> Is the defaultGoal a domain of the developer (as it is used above) or
> should it be for an end user, e.g. where I have seen it used for 'mvn
> install'.
No idea; I always specify something to do.
Before a commit, I generally run
$ mvn site site:stage
and have a look at the generated reports (mainly CheckStyle).
Regards,
Gilles
>
> Alex
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org