Re: Excessive "checking for updates" on Travis CI

Hi Mark, On 29/06/17 19:50, Mark Raynsford wrote: On 2017-06-29T19:38:40 +0200 Karl Heinz Marbaise wrote: HI, first you are using version ranges...that's the reason for that... Simple recommendation I can give is: Don't use version ranges... Hello. I maintain ~70

Re: Excessive "checking for updates" on Travis CI

Hi Mark, On 30/06/17 11:44, Mark Raynsford wrote: Apologies if that came off as rude, it wasn't intended to be. Upon re-reading it, I think it came off as a bit harsh. No problem. It's a real good behaviour of yours that you appologize for that...which I didn't take as rude etc. Kind

Re: Excessive "checking for updates" on Travis CI

Apologies if that came off as rude, it wasn't intended to be. Upon re-reading it, I think it came off as a bit harsh. M pgppS5LvgbIs9.pgp Description: OpenPGP digital signature

Re: Excessive "checking for updates" on Travis CI

On 2017-06-29T19:38:40 +0200 Karl Heinz Marbaise wrote: > HI, > > first you are using version ranges...that's the reason for that... > > Simple recommendation I can give is: Don't use version ranges... > > Hello. I maintain ~70 projects with complex interdependencies

Re: Excessive "checking for updates" on Travis CI

HI, first you are using version ranges...that's the reason for that... Simple recommendation I can give is: Don't use version ranges... Kind regards Karl Heinz Marbaise On 29/06/17 19:13, Mark Raynsford wrote: Hello. I use the free Travis CI service to build my various projects on each

Excessive "checking for updates" on Travis CI

Hello. I use the free Travis CI service to build my various projects on each commit. I have a project that has a rather large number of modules (~90) and upon building each module, I see lots of this in the log: [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for