When I was writing my LifecycleExtension recently I hit this same issue, with the two different logger classes depending on where my common code was being called from.
I just changed my base code to accept a Consumer<String> and passed in getLog()::info and the relevant other method from the other logger as method references. Worked a charm in my small use case anyway. On Sat, Jul 2, 2016 at 12:35 AM, Grzegorz Słowikowski < [email protected]> wrote: > I didn't want to depend on 'maven-embedder', so my first thought was to > copy this class, change 'org.slf4j.Logger' class of the 'logger' > variable to 'org.apache.maven.plugin.logging.Log', I have (in > 'AbstractMojo') > > Advantage - I control the class > Disadvantages - e.g. no colors in future Maven versions (because using > class from Maven not supporting colors yet), licensing questions > -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree
