Raul Miller wrote: > On Fri, Feb 22, 2008 at 6:50 AM, Chris Burke <[EMAIL PROTECTED]> wrote: >> We cannot always update JAL before a distribution, since the scripts may >> have changes that depend on changes to the J engine. After the >> distribution is made, JAL can be updated, as happened already today. >> However, this is still a manual process, so there may be a delay. > > Any chance you could add some kind of "client J version" support to JAL? > > Conceptually, this would mean that you have a different server collection for > JAL for each J engine release, though practically speaking you would probably > want some mechanism like "the main JAL library is for our most recent dev > copy and for each back version which requires different files we have > a collection > of files which need to be different for that version of J". Or maybe you even > make it so J can talk directly with your SVN repository and manage JAL that > way...
Right now JAL distinguishes J version number (601 vs 602), but not releases within version numbers (m beta vs n beta) - I suspect this would be more trouble than it is worth. We could avoid the problem Bill raised by making Package Manager not install any packages whose JAL version number is less than the current installed version. Although we don't talk directly with the SVN repository, what we have is pretty close to that with the addons, as each SVN commit triggers an immediate JAL build. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
