Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
remove old cvs property
COMMONSSITE-30 - fix the checkstyle configuration to work for multi-module and review/update <reporting> plugin version numbers for the poms being changed.
- 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)
Change source distro to unpack to a different directory
TLP related blanket changes: s:jakarta.apache.org/commons:commons.apache.org: s/commons-user@jakarta.apache.org/user@commons.apache.org/ s/commons-dev@jakarta.apache.org/dev@commons.apache.org/ s/Jakarta Commons/Apache Commons/ s:svn.apache.org/viewcvs/jakarta/commons:svn.apache.org/viewvc/commons: s:svn.apache.org/viewcvs.cgi/jakarta/commons:svn.apache.org/viewvc/commons: s:svn.apache.org/viewvc/jakarta/commons:svn.apache.org/viewvc/commons: s:svn.apache.org/repos/asf/jakarta/commons:svn.apache.org/repos/asf/commons: I'd appreciate another pair of eyes on this. There are some categories we probably don't want to change ATM (hopefully, none of these snuck in): * Historicals (proposals etc.) * URLs that shouldn't change (DOCTYPE fragments etc.) * Test cases where namespace URLs matter etc. (I'll track any related nightly failures)
Moving to TLP
Moving back :)
Moving to TLP
Configure m1 build to do checkstyle
Setting the maven repo - apologies if this borks anything
Moved copyright out of source files and into NOTICE.txt
Various build/site changes: - remove dependency on commons-build - update maven build to add missing files from src/binary distros - update maven build to generate checksums - de-tab project.xml - correct archive info regarding previous releases on index page - Improve Issue Tracking - Add "Building" page - Add "Changes Report" - Add "Downloads" page - Improve site navigation
Modify maven build to add two non-standard attributes to the jar's manifest file to indicate the values of "maven.compile.source" and "maven.compile.target". Also modify the build to include an "Implementation-Vendor-Id" of "org.apache" in the jar's manifest. 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
svn:keywords correction
Use SVN changelog
Change to Apache License 2.0
Adding Commons Site Look & Feel configuration to all jakarta-commons/<project>/project.properties
Upgraded maven site generation in preparation for switching to maven
Updated most of the commons project.properties files, made sure that the dev process points to the commons charter. Also, changed the powered by logo to use the less distracting feather logo
Added documentation properties
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |