Re: Excessive "checking for updates" on Travis CI

2017-06-29 Thread Mark Raynsford 
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 (this graph
shows a subset of them):

  https://raw.githubusercontent.com/io7m/universe/master/io7m.png

If I don't use version ranges, then when I update one dependency, I get
to update a ton of other packages too. I make frequent releases. Without
version ranges, my day would quickly be consumed by
version-number-incrementing busy work across a large number of packages
instead of getting actual development work done.

I make strong guarantees about API compatibility with my own packages,
including using japicmp to analyze the bytecode to ensure that I follow
semantic versioning correctly. Therefore, I use version ranges, and
have been for years.

Is there something else I could be doing?

M


pgpOYDjUHgnE8.pgp
Description: OpenPGP digital signature

Re: Excessive "checking for updates" on Travis CI

2017-06-29 Thread Karl Heinz Marbaise 

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

Excessive "checking for updates" on Travis CI

2017-06-29 Thread Mark Raynsford 
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


pgpI6ScSuvePM.pgp
Description: OpenPGP digital signature

Apache Parent 19 schedule?

2017-06-29 Thread Mike Drob 
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

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

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

2017-06-29 Thread djeanprost 
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 Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org