Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
Update to commons-parent-12
Upgrade to latest clirr plugin version 2.2.2 (fixes problem downloading the old artifact from the repo)
change commons-parent to version 11
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)
Upgrade to commons-parent-10 pom
Upgrade to version 9 of commons-parent
Remove the maven-site-plugin version - now specified in commons-parent pom
Revert logging to surefire 2.3 (fails with surefire 2.4.2) and remove the compile target config which is now fixed in commons-parent
Upgrade to commons-parent-8 and add configuration properties for OSGi (maven-bundle-plugin) and commons-build-plugin
upgrade to commons-parent-7
Upgrade to commons-parent version 6 release
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release commons-logging-1.1.1
Go back to previous version and add back the license.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release commons-logging-1.1.1
[LOGGING-118] Generate source and binary archives. Replace the single assembly with separate source and binary assemblies.
Go back to previous version again.
Use the correct value for the X-Compile-Target-JDK manifestEntry. Add the attributes Built-By, X-Compile-Source-JDK and X-Compile-Target-JDK to the manifest for the -api and -adapters jar files.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release commons-logging-1.1.1
Go back to previous version.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release commons-logging-1.1.1
Use the released version of commons-parent 5.
Specify that we are using JIRA.
Back up to previous version. Use the latest parent to be able to use the maven-remote-resources-plugin.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release commons-logging-1.1.1
Move deploy plugin configuration to release profile.
Add a ci profile that has the snapshot repositories configured.
Solve release related issues.
Add missing groupIds.
Back up to previous version. Fix the names of the assembly's checksums.
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release commons-logging-1.1.1
Add schema to project. Remove redundant elements. Do not use line-breaks within tags.
Lock down the version for maven-site-plugin.
Add a clirr report.
Specify versions for maven-antrun-plugin and maven-assembly-plugin.
Changing name to 'Commons Xxx'
Updated commons parent version to 4.
Moving to TLP
Moving back :)
Moving to TLP
Attach the adapters and api jars to the normal artifact. This way they will be deployed when the normal artifact is deployed.
Remove jakarta references from m1 and m2 builds
- Add an antrun execution to copy site resources. - Set the scope of servlet-api to provided. - Add the jdepend-maven-plugin report. - Set maven.compile.target to 1.1 to match the value used in the Ant build. - Remove the bogus repository from distributionManagement. - Fix the site url in distributionManagement.
Update to a more recent parent and remove stuff that is inherited from that parent.
Add missing developerConnection. Update to a released parent and remove stuff that is available in that version of the parent. Add properties to compile for Java 1.2.
Add a combined source and binary assembly. It differs from the one produced by Ant in these areas: - the docs folder is called site - the complete src/ directory is included, not just src/java/ - all files necessary to build the product using Ant, Maven 1 and Maven 2 are included - the *-ide.zip file is not created or included
Remove reference to old maven-xdoc-plugin. Add the same reports as for Maven 1: javadoc, jdepend, cross reference and test results.
First try at a Maven 2 generated site. Requires commons-parent 2-SNAPSHOT because it inherits parts of the site.xml from it.
Fix issue management url.
Add our own manifest to all the produced jar files.
Set EOL style to native. No real changes has been made to the code.
Add note re how to run unit tests.
Fix use of optional dependencies; optional is a separate flag, not a scope. Thanks to Wendy Smoak for pointing this out.
Add comments about unusual dependency-handling approach.
Trivial change; add newline after license.
Hooking to the newly released v1 commons-parent pom
Making sure all the pom.xmls have NOTICE/LICENSEs in - though haven't done VFS
Points to the commons-parent now
Copy resources into test jar. Also minor layout tidyups.
Rework packaging phase. JCL now builds correctly with maven2 (though unit tests don't run).
Initial attempt at building commons-logging using maven2; not fully functional yet.
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 |