You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jon Harper <jo...@gmail.com> on 2019/05/17 13:53:54 UTC

Maven-enforcer-plugin dependency convergence verbose logs

Hi list,
using maven-enforcer-plugin dependency converge rule, the logs of the
trees of the conflicting dependencies represent 7000 lines out of the
12000 lines of logs of my build.

Would it be possible to allow configuring the verbosity of the plugin
? Either with an explicit configuration flag, or by using more fine
grained loggers so that the user can configure them using slf4j ?

A simple change would be to change the log of the trees to the INFO so
that users can configure
org.slf4j.simpleLogger.log.org.apache.maven.plugins.enforcer to WARN
(either on the command line, or in .mvn/jvm.config or in
$MAVEN_HOME/conf/logging/simplelogger.properties  )

For example on this example log, removing the trees would still leave
useful logs but remove a lot of noise.

>> [WARNING]
>> Dependency convergence error for org.openrdf.sesame:sesame-rio-api:2.7.12 paths to dependency are:
>>     +-com.blazegraph:bigdata-core:2.1.4
>>       +-org.openrdf.sesame:sesame-runtime:2.7.12
>>         +-org.openrdf.sesame:sesame-repository-api:2.7.12
>>           +-org.openrdf.sesame:sesame-rio-api:2.7.12
>> and
>> +-com.powsybl:powsybl-distribution-core:3.0.0-SNAPSHOT
>>   +-com.powsybl:powsybl-triple-store-impl-blazegraph:3.0.0-SNAPSHOT
>> [..snip 200 lines of trees..]
>>
>> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
>> Failed while enforcing releasability. See above detailed error message.

What do you think ?

Cheers,
Jon

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Maven-enforcer-plugin dependency convergence verbose logs

Posted by Enrico Olivelli <eo...@gmail.com>.
Hi Jon,
I think that if this idea can help you it is worth to work on it.
Can you create a JIRA with your case ?
It would be great if you can also try to send a pull request with a
proposal,
We will be happy to see your code and eventually merge it.

Cheers
Enrico

Il sab 18 mag 2019, 06:48 Jon Harper <jo...@gmail.com> ha scritto:

> Hi list,
> using maven-enforcer-plugin dependency converge rule, the logs of the
> trees of the conflicting dependencies represent 7000 lines out of the
> 12000 lines of logs of my build.
>
> Would it be possible to allow configuring the verbosity of the plugin
> ? Either with an explicit configuration flag, or by using more fine
> grained loggers so that the user can configure them using slf4j ?
>
> A simple change would be to change the log of the trees to the INFO so
> that users can configure
> org.slf4j.simpleLogger.log.org.apache.maven.plugins.enforcer to WARN
> (either on the command line, or in .mvn/jvm.config or in
> $MAVEN_HOME/conf/logging/simplelogger.properties  )
>
> For example on this example log, removing the trees would still leave
> useful logs but remove a lot of noise.
>
> >> [WARNING]
> >> Dependency convergence error for
> org.openrdf.sesame:sesame-rio-api:2.7.12 paths to dependency are:
> >>     +-com.blazegraph:bigdata-core:2.1.4
> >>       +-org.openrdf.sesame:sesame-runtime:2.7.12
> >>         +-org.openrdf.sesame:sesame-repository-api:2.7.12
> >>           +-org.openrdf.sesame:sesame-rio-api:2.7.12
> >> and
> >> +-com.powsybl:powsybl-distribution-core:3.0.0-SNAPSHOT
> >>   +-com.powsybl:powsybl-triple-store-impl-blazegraph:3.0.0-SNAPSHOT
> >> [..snip 200 lines of trees..]
> >>
> >> [WARNING] Rule 0:
> org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
> >> Failed while enforcing releasability. See above detailed error message.
>
> What do you think ?
>
> Cheers,
> Jon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>