https://bugzilla.redhat.com/show_bug.cgi?id=1351822
--- Comment #1 from Mikolaj Izdebski <mizdebsk(a)redhat.com> ---
(In reply to Christopher Tubbs from comment #0)
Maven 3 added colorized logging support via log4j2. However, the
default
installation of maven does not add log4j-slf4j (slf4j binding to log4j2) or
an appropriate log4j2.xml file for colorized output.
Maven upstream is currently working on adding out-of-the-box colorization in
next major release (3.4.0). Maybe you can just wait for it?
Worse, the way maven loads its dependencies (symlinks in
/usr/share/maven/lib/* and /usr/share/maven/lib/ext/*) make it difficult for
users to configure colorization without those settings being clobbered by an
RPM update (because it's a classpath decision which isn't set in /etc).
There are multiple ways of customizing Maven installation by editing config
files, either globally or only for specific users (doesn't even require root
access). If you want equivalent of globally adding JARs to lib/ or lib/ext/
then you can simply edit /etc/m2.conf and list arbitrary JARs there. This
config file is marked as %config(noreplace), so it won't be updated by RPM. You
don't need to remove slf4j-simple.jar - SLF4J warnings about multiple bindings
can be avoided by using more advanced Maven class loading tricks, like creating
separate class realm "log4j" and making "plexus.core" import classes
from it.
Example m2.conf is attached. Let me know if you need more information.
Additionally, there's an annoying bug in Maven 3.3.3 which gives
a warning
when switching to colorized output:
https://issues.apache.org/jira/browse/MNG-5961
This one I can patch in Fedora.
--
You are receiving this mail because:
You are on the CC list for the bug.