Ok, will submit a patch for this early next week. Current plan is to use a properties file (versioninfo.properties) that will be generated from the ant build script and contain the release version/name, the source repository, a revision indicator (number, tag, or digest), and who built it.
All the properties may be defined on the command line when running "ant jar". If the properties are not defined, the ant updated build script will try to determine them. The versioninfo.properties file will be included in the jar and loaded by core.clj. Two considerations: * Should we store the properties as a Clojure map instead of as a Java properties file? * Should we generalize "versioninfo.properties" to "clojure.properties" with a "version" prefix? E.g., "version.release- name". -Matt On Nov 14, 2008, at 11:43 AM, "Graham Fawcett" <[EMAIL PROTECTED]> wrote: > > On Sat, Nov 8, 2008 at 12:03 PM, Matt Revelle <[EMAIL PROTECTED]> > wrote: >> >> If marking SVN revisions and/or release versions is something we >> still >> want and want automated, it now looks like using the build tool is >> the >> only way to go. The example I sent earlier to the list includes the >> creation of a "versioninfo" file from the build script which is then >> read and stored in a "version" var in boot.clj. >> >> The only problem is that the build script now depends on the >> "svnversion" command being available and a SVN repository being used >> for building. For tarball releases of the source, the "versioninfo" >> file can be generated for the release and the build script modified >> to >> use the existing file if "svnversion" isn't working. As for >> supporting git and other SCMs used to mirror the SVN repos, the build >> script can be made to use the tools available in any of the other >> SCMs >> to identify the SVN revision and generate the "versioninfo" file. > > +1. I think it's worth it, and would really like to see this put in > place. > > Best, > Graham > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
