Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In some future, MD5Checker and/or the build.xml could be improved to auto-update the sdk-installer-config-4.0.xml automatically, without human intervention, but that would imply leaving SVN credentials on the CI Server and I am not willing to put my credentials on that machine.  Also, I haven't found a way to "hit the publish button" in ASF CMS through Ant.  I think it is possible if someone wants to try.

Adding New Entries

To add a new entry, copy an existing entry and update the tag name from VersionAA to VersionAB or whatever is next in the sequence.  Update occurrences of the old version number to the new version number so that the right URL is represented.  No need to worry about the cacheIDs or MD5 entry.  Then save it, commit it to SVN, and publish it.  Then go run MD5Checker locally and follow the update steps above.  You could try to get the cachdID and MD5 entries right by computing the MD5 with some utility and sniffing the eTag header with some packet sniffer, but IMO, it isn't worth it and you might as well check that MD5Checker can read your changes to the sdk-installer-config-4.0.xml file.