You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@apache.org by Robert Munteanu <ro...@apache.org> on 2013/07/24 13:55:02 UTC

[jenkins] Console output full of unexpected statements: org.apache.maven.cli.event.ExecutionEventLogger mojoStarted

Hi,

I noticed that the build output is now full of debugging (?)
statements , such as

Jul 24, 2013 11:54:09 AM
org.apache.maven.cli.event.ExecutionEventLogger projectStarted
Jul 24, 2013 11:54:10 AM
org.apache.maven.cli.event.ExecutionEventLogger mojoStarted

See the sling-trunk-1.7 job [1] for instance. Are these needed? They
make the log pretty hard to read.

Robert

[1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/136/console

Re: [jenkins] Console output full of unexpected statements: org.apache.maven.cli.event.ExecutionEventLogger mojoStarted

Posted by Olivier Lamy <ol...@apache.org>.

correct.
Jenkins now use slf4j on top of jul.
I will try to change that with configuring a logging.properties file


2013/7/24 Robert Munteanu <ro...@apache.org>:
> Hi,
>
> I noticed that the build output is now full of debugging (?)
> statements , such as
>
> Jul 24, 2013 11:54:09 AM
> org.apache.maven.cli.event.ExecutionEventLogger projectStarted
> Jul 24, 2013 11:54:10 AM
> org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
>
> See the sling-trunk-1.7 job [1] for instance. Are these needed? They
> make the log pretty hard to read.
>
> Robert
>
> [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/136/console



-- 
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy