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

Apache Parent 19 schedule?

Hi Maven Team, Is there a schedule for parent 19 release? There's been some plugin version updates, I'm not sure if there are other improvements that can be made related to maven 3.5.0 existing, but either way it's been over a year since the last update. What do y'all think? Thanks, Mike

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

Re: problem when deploying to nexus with a password with accent

Issue created in maven jira : MNG-6245 -- View this message in context: http://maven.40175.n5.nabble.com/problem-when-deploying-to-nexus-with-a-password-with-accent-tp5910070p5910528.html Sent from the Maven - Users mailing list archive at