Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_3_RC4
Prepare for RC4
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_3_RC3
Uploading to RC3 directory
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_3_RC3
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_3_RC2
Preparing for 1.3 RC2
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_3_RC1
Rolling back release attempt
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_3_RC1
Preparing for 1.3 release
Fix PMD 1.5 warnings
Updating compiler plugin separately (why did this ever work before?)
Merging in Java5 branch; eliminated compiler warnings
Update to commons-parent-12
Adding release profile distributionManagement
JUnit 3.8.2 is the best available for Java 1.4
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_2
Screwed up RC3 attempt, trying again
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_2
Rolling back to prepare for RC3
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_2
Prepare pom to release 1.2 RC2
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release DBUTILS_1_2
Explicitly depend on jdk 1.4
Add charset to help SVN mailer display changes correctly
Fix encoding of Péter Bagyinszki's name
Backporting changes that release:prepare would have made, trying to avoid clobbering the apache license
Updating pom in preparation for 1.2 RC1, as per CreatingReleases wiki. I'm not sure I quite understand the purpose of the rc profile I'm adding, but I'm sure it's all for the best!
Adding myself to the dev list
Deleting the suite concept and telling M2 to go build the tests and ignore the base class. That way new tests will be autoadded rather than being missed.
Merging in Dab Fabulich's work on https://svn.apache.org/repos/asf/commons/sandbox/dbutils/bugfixing from -r741987:747723. Resolving DBUTILS-34 - DBUTILS-37 - DBUTILS-29 - DBUTILS-14 - DBUTILS-31 - DBUTILS-39 - DBUTILS-41 - DBUTILS-44 - DBUTILS-33 - DBUTILS-42 - DBUTILS-40
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 redundant <resource> configuration for NOTICE/LICENSE - these are configured in commons-parent (NOTE: seems that components which define other <resource> elements need to include these - so only removing from components where NOTICE/LICENSE are the only resources configured)
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
Update m2 build
Changing name to 'Commons Xxx'
Fixing the user svn url
Updated commons parent version to 4.
Moving to TLP
Moving back :)
Moving to TLP
Remove jakarta references from m1 and m2 builds
Update pom version, fix scm urls
Match groupIds for m1 and m2. We should account for the fact that its relatively easier to deploy snaps with m2 (such as IO was last night) and we shouldn't spray component artifacts in two different places (without relocation).
Missing props on various m2 poms.
Moving to create a 1.1 that can then be voted on
Hooking to the newly released v1 commons-parent pom
Making sure all the pom.xmls have NOTICE/LICENSEs in - though haven't done VFS
Adding a Maven 2 pom
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 |