You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Eric Pugh <ep...@opensourceconnections.com> on 2004/10/22 15:44:30 UTC

Controlling Logging Output of Plugins?

Hi all,

the jxr plugin is dumping lots of these messages:

 PackageManager -> parsing... com\upstate\commons\turbine\om\BaseObject.java
PackageManager -> parsing...
com\upstate\commons\turbine\pulltool\CustomerTool.java
PackageManager -> parsing...
com\upstate\commons\turbine\pulltool\FormatTool.java
PackageManager -> parsing...
com\upstate\commons\turbine\pulltool\SessionPageData.java


I thought that maybe this was because I had a log4j.properties file in my
path, and it was being picked up..  But, I can't seem to turn it off.  I
added

log4j.category.org.apache.maven.jxr.pacman.PackageManager=WARN

to try..  To customize logging, do I need to put a log4j.properties in my
MAVEN_HOME/libs directory?

Related, there seems to be a bunch of out of date methods etc in JXR..
Anyone mind if I remove the extra unused logging methods like one that does
System.out.println?

Argh,
Eric


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Controlling Logging Output of Plugins?

Posted by Brett Porter <br...@apache.org>.
Yes, but you can control that by the logger name (or package).

Not ideal, but works...

- Brett

Eric Pugh wrote:

>Okay..  That is what I thought..  But, that means that I controle the
>logging at the level of my Maven install, versus at the level of my
>indivdual project.
>
>Eric
>
>  
>
>>-----Original Message-----
>>From: Brett Porter [mailto:brett@apache.org]
>>Sent: Saturday, October 23, 2004 12:30 AM
>>To: Maven Developers List
>>Subject: Re: Controlling Logging Output of Plugins?
>>
>>
>>Any removal of System.out is a Good Thing.
>>
>>To customise log4j, you must override log4j.properties in maven.jar
>>using the standard log4j initialisation technique (eg
>>-Dlog4j.properties=...)
>>
>>- Brett
>>
>>Eric Pugh wrote:
>>
>>    
>>
>>>Hi all,
>>>
>>>the jxr plugin is dumping lots of these messages:
>>>
>>>PackageManager -> parsing...
>>>      
>>>
>>com\upstate\commons\turbine\om\BaseObject.java
>>    
>>
>>>PackageManager -> parsing...
>>>com\upstate\commons\turbine\pulltool\CustomerTool.java
>>>PackageManager -> parsing...
>>>com\upstate\commons\turbine\pulltool\FormatTool.java
>>>PackageManager -> parsing...
>>>com\upstate\commons\turbine\pulltool\SessionPageData.java
>>>
>>>
>>>I thought that maybe this was because I had a log4j.properties file in my
>>>path, and it was being picked up..  But, I can't seem to turn it off.  I
>>>added
>>>
>>>log4j.category.org.apache.maven.jxr.pacman.PackageManager=WARN
>>>
>>>to try..  To customize logging, do I need to put a log4j.properties in my
>>>MAVEN_HOME/libs directory?
>>>
>>>Related, there seems to be a bunch of out of date methods etc in JXR..
>>>Anyone mind if I remove the extra unused logging methods like
>>>      
>>>
>>one that does
>>    
>>
>>>System.out.println?
>>>
>>>Argh,
>>>Eric
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>>
>>>
>>>
>>>      
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>For additional commands, e-mail: dev-help@maven.apache.org
>>    
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>  
>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


RE: Controlling Logging Output of Plugins?

Posted by Eric Pugh <ep...@upstate.com>.
Okay..  That is what I thought..  But, that means that I controle the
logging at the level of my Maven install, versus at the level of my
indivdual project.

Eric

> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: Saturday, October 23, 2004 12:30 AM
> To: Maven Developers List
> Subject: Re: Controlling Logging Output of Plugins?
>
>
> Any removal of System.out is a Good Thing.
>
> To customise log4j, you must override log4j.properties in maven.jar
> using the standard log4j initialisation technique (eg
> -Dlog4j.properties=...)
>
> - Brett
>
> Eric Pugh wrote:
>
> >Hi all,
> >
> >the jxr plugin is dumping lots of these messages:
> >
> > PackageManager -> parsing...
> com\upstate\commons\turbine\om\BaseObject.java
> >PackageManager -> parsing...
> >com\upstate\commons\turbine\pulltool\CustomerTool.java
> >PackageManager -> parsing...
> >com\upstate\commons\turbine\pulltool\FormatTool.java
> >PackageManager -> parsing...
> >com\upstate\commons\turbine\pulltool\SessionPageData.java
> >
> >
> >I thought that maybe this was because I had a log4j.properties file in my
> >path, and it was being picked up..  But, I can't seem to turn it off.  I
> >added
> >
> >log4j.category.org.apache.maven.jxr.pacman.PackageManager=WARN
> >
> >to try..  To customize logging, do I need to put a log4j.properties in my
> >MAVEN_HOME/libs directory?
> >
> >Related, there seems to be a bunch of out of date methods etc in JXR..
> >Anyone mind if I remove the extra unused logging methods like
> one that does
> >System.out.println?
> >
> >Argh,
> >Eric
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Controlling Logging Output of Plugins?

Posted by Brett Porter <br...@apache.org>.
Any removal of System.out is a Good Thing.

To customise log4j, you must override log4j.properties in maven.jar 
using the standard log4j initialisation technique (eg 
-Dlog4j.properties=...)

- Brett

Eric Pugh wrote:

>Hi all,
>
>the jxr plugin is dumping lots of these messages:
>
> PackageManager -> parsing... com\upstate\commons\turbine\om\BaseObject.java
>PackageManager -> parsing...
>com\upstate\commons\turbine\pulltool\CustomerTool.java
>PackageManager -> parsing...
>com\upstate\commons\turbine\pulltool\FormatTool.java
>PackageManager -> parsing...
>com\upstate\commons\turbine\pulltool\SessionPageData.java
>
>
>I thought that maybe this was because I had a log4j.properties file in my
>path, and it was being picked up..  But, I can't seem to turn it off.  I
>added
>
>log4j.category.org.apache.maven.jxr.pacman.PackageManager=WARN
>
>to try..  To customize logging, do I need to put a log4j.properties in my
>MAVEN_HOME/libs directory?
>
>Related, there seems to be a bunch of out of date methods etc in JXR..
>Anyone mind if I remove the extra unused logging methods like one that does
>System.out.println?
>
>Argh,
>Eric
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>  
>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org