maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cleuton Sampaio <>
Subject Re: Maven Plugin Logging
Date Fri, 03 Jan 2014 23:15:11 GMT
You should use the object returned by the getLog method, which is an implementation of 

Interface Log

It is exactly the architecture that I am using in my own plugin: jQana (Github). It is still
in early dev stage, but I am facing that same problem. The only way to solve is to use the
Log implemantation returned by getLog. 

Here I am instantiating my pojo from the mojo, and passing the Log Object:

                        DefaultProjectProcessor dpp = new DefaultProjectProcessor(new Context());

Here I am logging in my pojo:

                         // using maven plugin logger
                         switch (type) {
                         case INFO:
                         case DEBUG:
                         case ERROR:

Cleuton Sampaio

> Em 03/01/2014, às 18:46, "Omar@Gmail" <> escreveu:
> Thanks Cleuton, in my custom plugin which I developed I have a Mojo that
> extends AbstractMojo but this Mojo delegates to a Pojo. Both the Mojo and
> Pojo each have  their won logger. In this case does your suggestion still
> stand? can you suggest some simple steps to use the AbstractMojo getLog()
> method.
> Omar
>> On 3 January 2014 16:02, Cleuton Sampaio <> wrote:
>> Did you based your mojo on class AbstractMojo ?  If you did, then you
>> should use the getLog() method. See:
>> Cleuton Sampaio
>>>> Em 03/01/2014, às 07:44, "Omar@Gmail" <>
>>> escreveu:
>>> Hi All,
>>> I implemented my own Maven plugin mojo in which I used log4j + slf4j. In
>>> the plugin project I have included the correct jars and can see correct
>>> logging of statements from code.
>>> Now I want use this new maven plugin in another client project but having
>>> trouble getting it to work correctly.
>>> In the plugin itself I have included a under
>>> src/main/resources which works fine as mentioned above. But when I try to
>>> include the plugin in another client project the log file is not being
>>> created.
>>> The question is what else do I have to try or do to get this working
>>> correctly?
>>> Thank you.
>>> Omar
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message