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 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 updates from sonatype [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.jequality:com.io7m.jequality.core: checking for updates from sonatype [INFO] artifact com.io7m.jequality:com.io7m.jequality.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.jtensors:com.io7m.jtensors.core: checking for updates from sonatype [INFO] artifact com.io7m.jtensors:com.io7m.jtensors.core: checking for updates from sonatype-apache [INFO] artifact it.unimi.dsi:fastutil: checking for updates from sonatype [INFO] artifact it.unimi.dsi:fastutil: checking for updates from sonatype-apache [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype [INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.jtensors:com.io7m.jtensors.storage.bytebuffered: checking for updates from sonatype [INFO] artifact com.io7m.jtensors:com.io7m.jtensors.storage.bytebuffered: checking for updates from sonatype-apache [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype [INFO] artifact com.io7m.mutable.numbers:com.io7m.mutable.numbers.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype [INFO] artifact com.io7m.jnull:com.io7m.jnull.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype [INFO] artifact com.io7m.junreachable:com.io7m.junreachable.core: checking for updates from sonatype-apache [INFO] artifact com.io7m.ieee754b16:com.io7m.ieee754b16.core: checking for updates from sonatype [INFO] artifact com.io7m.ieee754b16:com.io7m.ieee754b16.core: checking for updates from sonatype-apache Note that not only are these artifacts being checked redundantly (because an artifact may be checked at least once per module), they're also being checked multiple times in the same plugin execution! You can see an example of a build log here: https://api.travis-ci.org/jobs/248453940/log.txt I'm actually starting to hit the 4mb log file size limit on Travis due to the sheer amount of output produced. The project's source code, for the curious, is here: https://github.com/io7m/r2 Is there some way to get these redundant checks to stop? Failing that, is there a way to get Maven to shut up about it? M
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
