Closed GoogleCodeExporter closed 8 years ago
Hell yeah!!! Annoying as
Original comment by Sam.Boyc...@gmail.com
on 12 Sep 2012 at 6:01
[deleted comment]
OK - i realize i'm answering a mega old question - but that log message was
unacceptable for my final build. I have create a copy of the reflections jar
that has that logging line commented out.
This is an amazing library - love the work you guys are doing - keep it up
http://www.mediafire.com/?sb9jijfenrooj6q
Original comment by Sam.Boyc...@gmail.com
on 13 Sep 2012 at 4:09
Attachments:
I find this message useful but woud like the ability to set the debug level
(possibly on the Reflections constructor) so that I can see messages while
working but then turn them off for releases.
This package is great by the way.
Original comment by Mik3.R...@gmail.com
on 17 Sep 2012 at 11:48
Did the developers of this trash really thought it was that important to put
that INFO log. It just ruined my day.
Original comment by Gajduk.a...@gmail.com
on 27 Sep 2012 at 1:23
After reading the source code of the Reflections class I realize the logging
can be turned off.
The way it has been setup breaks good Java practices so it was confusing to
figure out.
The static field log of the Reflections class is public and the code is written
so that it can be set to null to turn logging off.
There is a Java Annotation of @Nullable on this field to indicate this, n.b.
@Nullable is not a valid Java Annotation.
Original comment by mr...@juolaassociates.com
on 7 Jan 2013 at 2:54
Original comment by ronm...@gmail.com
on 22 Nov 2013 at 8:53
Original issue reported on code.google.com by
james.r...@gmail.com
on 31 May 2012 at 4:44