Re: [Springframework-developer] Final preparations for 1.1 RC1

[<jue...@we...>]

> I'm a bit unsure how copying macro definitions to app resource =
locations
> works in practice: presumably we can only do this once to avoid
> overwriting customizations made by the user?  How would we manage =
updates
> made to the macros inside spring.jar in future releases?  It just =
sounds a
> bit kludgy to me, but I'm probably missing an obvious benefit.

> In my experience, the standard macros briefly outlined would be more
> useful - I guess if a  user really wanted to completely customize the
> macro set, s/he could manually take a copy from the Spring source and =
do
> so, but I'm definitely open to opinions here.

On reflection, I tend to agree: Let's provide such default macros in =
spring.vm/ftl, even if containing HTML code. An application developer =
can always override through own macro libraries, potentially copying and =
modifying from the spring.vm/ftl files.=20
=20
I've added spring.vm/ftl to the build script, to copy them into the dist =
directory, alongside spring.tld and spring-beans.dtd. All of those are =
documented quite nicely in the source files, so should be easily =
available for review, even if contained in spring.jar anyway.
=20
Juergen