maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <mgai...@hotmail.com>
Subject RE: Debugging output only for a subproject in a reactor run
Date Tue, 01 Apr 2014 00:32:34 GMT
log4j.properties:

 

# OpenSymphony Stuff FATAL Error messages only
log4j.logger.com.opensymphony=FATAL


#Struts core debug (LOTS of messaging)

log4j.logger.org.apache.struts2=DEBUG

 

# Spring Stuff (lighten up to INFO Level)
log4j.logger.org.springframework=INFO


https://logging.apache.org/log4j/1.2/manual.html
HTH
Martin 
______________________________________________ 


  



> From: christian.domsch@assentis.com
> To: users@maven.apache.org
> Subject: Debugging output only for a subproject in a reactor run
> Date: Mon, 31 Mar 2014 09:56:00 +0000
> 
> Hi all,
> 
> I have problems with a very specific plugin in our build and want to 
> enable debugging output only for the subproject in our overall build 
> setup. The commandline option -X enables debugging for the complete 
> execution, and I fear this would create too much output and might fail 
> the build due to memory problems... Now, is there a way to change the 
> logger during the build to enable debugging just for this one project? 
> (plugins running in pre and post phases to enable/disable that?)
> 
> Thanks,
> Christia
> 
> 
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message