maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6023) Regression: mvn -X broken due to commit ce580ea2fafd7638ee56e1d0574de95a37164322
Date Wed, 18 May 2016 21:06:12 GMT

    [ https://issues.apache.org/jira/browse/MNG-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289821#comment-15289821
] 

Michael Osipov commented on MNG-6023:
-------------------------------------

Christian, I have targeted this issue to 3.4.0 not to be forgotten because I have IT failures.
If this won't get resolved before 3.4.0, we should drop the commit and go on for now.

> Regression: mvn -X broken due to commit ce580ea2fafd7638ee56e1d0574de95a37164322
> --------------------------------------------------------------------------------
>
>                 Key: MNG-6023
>                 URL: https://issues.apache.org/jira/browse/MNG-6023
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line, Logging
>    Affects Versions: 3.4.0
>            Reporter: Michael Osipov
>            Assignee: Christian Schulte
>            Priority: Blocker
>             Fix For: 3.4.0
>
>
> In [ce580ea2fafd7638ee56e1d0574de95a37164322|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=ce580ea2fafd7638ee56e1d0574de95a37164322]
SLF4J was updated from 1.7.16 to 1.7.21. Use a snapshot of that commit and run {{mvn -X}}
and see that no debug output is printed. Something is either broken in our code now or in
SLF4J Simple.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message