- pom's need to use ${basedir} for configuration files as the multi-module profile is run from commons-parent, so if not specified it can't find those files
- the checkstyle configuration file needs to use ${checkstyle.header.file} for the headerFile property and <headerFile> element added to the plugin config in the pom.xml
- fix m1 checkstyle config to reflect the above where appropriate (specify header file property)
git-svn-id: https://svn.apache.org/repos/asf/commons/proper/logging/trunk@659438 13f79535-47bb-0310-9956-ffa450edef68
The two non-standard entires created in the manifest file will look something like the following:
X-Compile-Source-JDK: 1.3
X-Compile-Target-JDK: 1.3
This change serves two purposes:
1) To provide comfort to users regarding JVM compatibility.
2) Enable releases to be checked more easily for JVM compatibility.
The manifest specification indicates that "unknown" entries in the manifest file are ignored. These entries have been prefixed with "X-" which is a sometimes used "convention" for indicating non-standard entries.
See thread: http://tinyurl.com/839zh
git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@377558 13f79535-47bb-0310-9956-ffa450edef68
