For the core, I believe the external dependencies are Freemarker, OGNL, XWork, and Commons Logging. Of course, adding plugins adds dependencies, but that's another matter.
My heuristic is to stay current with the latest production release, unless there is a problem. Otherwise, people using the framework may run into conflicts Since we are a major consumer of most of these dependencies, it follows that we have a responsibility to stay current and help vet the latest releases. -Ted. On 1/22/07, Joe Germuska <[EMAIL PROTECTED]> wrote:
I'm also going to run my local development with a dependency on FM 2.3.8. I reviewed the release notes and there are no obvious compatibility issues, plus, of course, a handful of bug fixes. It seems to have been stable for almost six months, so it seems safe for us to move to it. Do we have any heuristics for deciding when to change versions of dependencies? For projects with a strong commitment to backwards compatibility, it should generally make sense to move forward pretty directly with minor releases, but considering how many external dependencies we have, it seems like "rules" or some semblance thereof might be helpful. Joe On 1/21/07, Ted Husted <[EMAIL PROTECTED]> wrote: > > We've been running against freemarker 2.3.4. Has anyone tried using 2.3.8? > > Should we update our dependency from 2.3.4 to 2.3.8 ? > > * http://freemarker.org/docs/app_versions.html > > It's been out since July. I'm updating some training materials, and > I'll try it here locally. > > -Ted. > > On 1/20/07, Joe Germuska <[EMAIL PROTECTED]> wrote: > >I see now that the syntax I was trying to use was > > added in Freemarker 2.3.7
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
