This renaming more intuitively expresses the relationship between
subprojects and the JAR artifacts they produce.
Tracking history across these renames is possible, but it requires
use of the --follow flag to `git log`, for example
$ git log spring-aop/src/main/java/org/springframework/aop/Advisor.java
will show history up until the renaming event, where
$ git log --follow spring-aop/src/main/java/org/springframework/aop/Advisor.java
will show history for all changes to the file, before and after the
renaming.
See http://chrisbeams.com/git-diff-across-renamed-directories
28 lines
718 B
XML
28 lines
718 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
|
|
|
|
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
|
|
|
|
<!-- Appenders -->
|
|
<appender name="console" class="org.apache.log4j.ConsoleAppender">
|
|
<param name="Target" value="System.out" />
|
|
<layout class="org.apache.log4j.PatternLayout">
|
|
<param name="ConversionPattern" value="%-5p: %c - %m%n" />
|
|
</layout>
|
|
</appender>
|
|
|
|
<logger name="org.springframework.beans">
|
|
<level value="warn" />
|
|
</logger>
|
|
|
|
<logger name="org.springframework.binding">
|
|
<level value="debug" />
|
|
</logger>
|
|
|
|
<!-- Root Logger -->
|
|
<root>
|
|
<priority value="info" />
|
|
<appender-ref ref="console" />
|
|
</root>
|
|
|
|
</log4j:configuration> |