Thanks sebb
I've added small blurbs about the scripts - and verified it actually
works the way I described it by publishing the site from my local
machine :-)
Stefan
On 2021-07-13, sebb wrote:
> I have added a script to build and update the staging site:
> commons-site-build.sh
> This was sup
>> Are there any tests that actually use the uid/gid of the current user?
>> Compress will no read them by itself, so the only place things could
>> fail was if we used native tar to create an archive. Is there such a
>> test? If so we could try to adapt the test in question.
On 2021-07-10, Henr
The Apache Commons Team is pleased to announce Apache Commons IO 2.11.0.
Commons IO is a package of Java 8 utility classes like java.io.
Changes in this version include:
Fixed Bugs:
o IO-741: FileUtils.listFiles does not list matching files if File
parameter is a symbolic link. Thanks to Zach S
>
>> > The pom would have to be
>> > updated to bind the other plugins from the default goal to this phase
>> with
>> > executions.
>>
>> Is there something to be changed so [Math] is aligned with [RNG]?
>>
>
> [RNG] also does not have executions specified for spotbugs or pmd.
> apache-rat and chec
On Wed, 14 Jul 2021 at 11:49, Gilles Sadowski wrote:
> Le mer. 14 juil. 2021 à 12:29, Alex Herbert a
> écrit :
> >
> > The default goal specifies extra targets. Currently it is:
> >
> > clean verify apache-rat:check checkstyle:check pmd:check spotbugs:check
> > javadoc:javadoc
> >
> > We could c
Le mer. 14 juil. 2021 à 12:29, Alex Herbert a écrit :
>
> The default goal specifies extra targets. Currently it is:
>
> clean verify apache-rat:check checkstyle:check pmd:check spotbugs:check
> javadoc:javadoc
>
> We could change the pom to bind these targets to a lifecycle phase [1] such
> as 'v
The default goal specifies extra targets. Currently it is:
clean verify apache-rat:check checkstyle:check pmd:check spotbugs:check
javadoc:javadoc
We could change the pom to bind these targets to a lifecycle phase [1] such
as 'verify'.
Looking at the pom for CM the checkstyle plugin is configure
Le mer. 14 juil. 2021 à 12:10, sebb a écrit :
>
> On Wed, 14 Jul 2021 at 10:29, Gilles Sadowski wrote:
> >
> > Le mer. 14 juil. 2021 à 11:16, sebb a écrit :
> > >
> > > On Wed, 14 Jul 2021 at 10:03, Gilles Sadowski
> > > wrote:
> > > >
> > > > Hi.
> > > >
> > > > Is it correct that
> > > > $
On Wed, 14 Jul 2021 at 10:29, Gilles Sadowski wrote:
>
> Le mer. 14 juil. 2021 à 11:16, sebb a écrit :
> >
> > On Wed, 14 Jul 2021 at 10:03, Gilles Sadowski wrote:
> > >
> > > Hi.
> > >
> > > Is it correct that
> > > $ mvn site site:stage
> > > and
> > > $ mvn
> > > behave differently (i.e.
Le mer. 14 juil. 2021 à 11:16, sebb a écrit :
>
> On Wed, 14 Jul 2021 at 10:03, Gilles Sadowski wrote:
> >
> > Hi.
> >
> > Is it correct that
> > $ mvn site site:stage
> > and
> > $ mvn
> > behave differently (i.e. that the latter would not run "CheckStyle" or
> > that it generates warnings i
On Wed, 14 Jul 2021 at 10:03, Gilles Sadowski wrote:
>
> Hi.
>
> Is it correct that
> $ mvn site site:stage
> and
> $ mvn
> behave differently (i.e. that the latter would not run "CheckStyle" or
> that it generates warnings instead of errors)?
Depends on what the POM defines as the default ta
Hi.
Is it correct that
$ mvn site site:stage
and
$ mvn
behave differently (i.e. that the latter would not run "CheckStyle" or
that it generates warnings instead of errors)?
In CM, we were used to detect all issues by running the former.
Is it expected that it's not the case anymore?
Thanks,
12 matches
Mail list logo
