Bug 1324832

Summary:	No debug output with -X
Product:	[Fedora] Fedora	Reporter:	Michael Simacek <msimacek>
Component:	maven	Assignee:	Mikolaj Izdebski <mizdebsk>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	akurtako, java-sig-commits, mizdebsk, msimacek, msrb
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	3.3.9-4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-20 08:19:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michael Simacek 2016-04-07 11:51:44 UTC

Description of problem:
Current version of maven in rawhide doesn't seem to produce debug output anymore.

Version-Release number of selected component (if applicable):
maven-3.3.9-3.fc24.noarch

How reproducible:
always

Steps to Reproduce:
1. rebuild something with mvn -X
2. observe the output

Actual results:
No debug log messages, only info and higher levels.

Expected results:
Debug level log messages.

Additional info:
The version in Fedora 23 works correctly. There was slf4j update, I suspect it might be related.

Comment 1 Mikolaj Izdebski 2016-04-07 21:45:18 UTC

Reproducible with slf4j >= 1.7.18
Caused by this commit: https://github.com/qos-ch/slf4j/commit/ac099e4
(slf4j initialization is early, before Maven is able to set logging properties)

Comment 2 Mikolaj Izdebski 2016-04-07 21:49:31 UTC

Workaround: set environmental variable before running Maven/XMvn: MAVEN_DEBUG_OPTS=-Dorg.slf4j.simpleLogger.defaultLogLevel=trace

Comment 3 Mikolaj Izdebski 2016-04-07 23:08:48 UTC

Fixed in maven-3.3.9-4

Comment 4 Mikolaj Izdebski 2016-04-07 23:16:50 UTC

I believe that this bug is fixed in maven-3.3.9-4,
which is available in Fedora Rawhide, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=752152

Comment 5 Fedora Update System 2016-04-07 23:19:05 UTC

maven-3.3.9-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-1d2cc863b9

Comment 6 Fedora Update System 2016-04-08 16:52:22 UTC

maven-3.3.9-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-1d2cc863b9

Comment 7 Fedora Update System 2016-04-15 03:19:52 UTC

maven-3.3.9-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Mikolaj Izdebski 2016-04-20 08:19:01 UTC

I believe that this bug is fixed in maven-3.3.9-4,
which is available in Fedora Rawhide, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=752152