There is not a way that is built in.
However, it is actually pretty easy to do...
1. Create your own startup action. For this guy to work (in the way I'm outlining below), you need to be able to use portal-impl.jar. I created mine directly in the source and copied the class into the ROOT/WEB-INF/classes directory, but it might also work from an EXT plugin:
package com.example;
import com.liferay.portal.kernel.events.SimpleAction;
import com.liferay.portal.util.PropsUtil;
import com.liferay.util.log4j.Log4JUtil;
import java.util.Properties;
import org.apache.log4j.Level;
public class LoggingStartupAction extends SimpleAction {
public void run(final String[] ids) {
// grab any values in the properties file(s) that start with "portal.logging." as these
// are the guys we want to use for new logging properties.
Properties props = PropsUtil.getProperties("portal.logging.", true);
if ((props == null) || (props.isEmpty())) {
// there are no logging properties defined
return;
}
// If we get here we have at least one logging property to deal with.
String priority;
for (String loggerName : props.stringPropertyNames()) {
// get the priority defined for the logger
priority = props.getProperty(loggerName, Level.INFO.toString());
// update the log4j stuff using Liferay's API...
Log4JUtil.setLevel(loggerName, priority);
}
// Done!
}
}
2. In your portal-ext.properties, set up the global startup action event handlers...
global.startup.events=com.liferay.portal.events.GlobalStartupAction,com.example.LoggingStartupAction
3. In your portal-ext.properties, define the loggers you want to apply at startup... You can either define new ones or change the logging levels for built-in ones:
portal.logging.com.example=DEBUG
portal.logging.com.example.util=INFO
portal.logging.com.liferay.jdbc=INFO
That should do it!
