maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MENFORCER-314) DependencyConvergence fails sporadically with a null message
Date Sat, 27 Oct 2018 15:36:00 GMT


ASF GitHub Bot commented on MENFORCER-314:

famod commented on issue #44: [MENFORCER-314] - Include entire exception if message is missing
   Alternative approach to #43 which I actually like better but I am not sure.
   Please merge whichever PR you like best.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> DependencyConvergence fails sporadically with a null message
> ------------------------------------------------------------
>                 Key: MENFORCER-314
>                 URL:
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>          Components: Standard Rules
>    Affects Versions: 1.4.1
>         Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Java version: 1.8.0_162, vendor: Oracle Corporation
>            Reporter: Falko Modler
>            Priority: Major
> Our Jenkins builds fail sporadically without providing a message:
> {noformat}
> 17:08:28 [WARNING] Rule 4: org.apache.maven.plugins.enforcer.DependencyConvergence failed
with message:
> 17:08:28 null
> {noformat}
> Looking at the code, I suspect that this can happen [on line 132 of the rule|]
when some underlying exception is caught which itself does not provide a (localized) message.
> As the plugin [does not include the cause|]
(unless {{failFast}} is set), you will just see a null message.

This message was sent by Atlassian JIRA

View raw message