On Wed, Aug 5, 2020 at 9:05 AM sebb <[email protected]> wrote:

> Actually it did not do what I expected; I was hoping it would fix the
> Github Action build.
> However, that uses a separate config file, which I have since changed.
>
> I guess we need to change both of them.
> The flag requires Maven 3.6.1 or later.
>

Yeah... I like to use the -V flag to see what Maven version a CI build
picks up. Handy.

Gary



>
> On Wed, 5 Aug 2020 at 13:45, Gary Gregory <[email protected]> wrote:
> >
> > On Wed, Aug 5, 2020 at 8:34 AM <[email protected]> wrote:
> >
> > > This is an automated email from the ASF dual-hosted git repository.
> > >
> > > sebb pushed a commit to branch master
> > > in repository https://gitbox.apache.org/repos/asf/commons-io.git
> > >
> > >
> > > The following commit(s) were added to refs/heads/master by this push:
> > >      new 6034619  Quieten Travis builds
> > > 6034619 is described below
> > >
> > > commit 60346192969abf6e6f50491597100ee86218c1be
> > > Author: Sebb <[email protected]>
> > > AuthorDate: Wed Aug 5 13:33:47 2020 +0100
> > >
> > >     Quieten Travis builds
> > > ---
> > >  .travis.yml | 5 +++--
> > >  1 file changed, 3 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/.travis.yml b/.travis.yml
> > > index d259f72..7fefb68 100644
> > > --- a/.travis.yml
> > > +++ b/.travis.yml
> > > @@ -29,8 +29,9 @@ matrix:
> > >      - jdk: openjdk-ea
> > >        env: JACOCO_SKIP=true
> > >
> > > +# --no-transfer-progress requires Maven 3.6.1+. Otherwise use
> --batch-mode
> > >  script:
> > > -  - mvn
> > > +  - mvn --no-transfer-progress
> > >
> >
> > Good find! We need this for all of our CI builds IMO.
> >
> > Gary
> >
> >
> > >
> > >  after_success:
> > > -  - mvn clean cobertura:cobertura coveralls:report -Ptravis-cobertura
> > > +  - mvn --no-transfer-progress clean cobertura:cobertura
> coveralls:report
> > > -Ptravis-cobertura
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to