On Fri, Jun 27, 2008 at 11:45 PM, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > First of all, sorry for crossposting again :-) > > 2008/6/28 Nathan Bubna <[EMAIL PROTECTED]>: >> If none of this finds a home in Spring or Tiles, i would be interested >> in bringing some of it over into VelocityTools. > > First of all, what is the best place for such a plugin? > IMHO it is Tiles, since we want to treat view technologies in the same > way (JSP, Velocity, FreeMarker are the same in front of Tiles :-D ). > OTOH there is already a Velocity Tool for Tiles 1. > Well, I can't decide :-)
VelocityTools 2 is extremely flexible at this point. Including a tool that lives in a separate library is very easy. Tiles could even include a tools.xml in its jar with the TilesTool configuration and most standard VelocityTools 2 users would automatically pick up the tool if they just add the tiles jar to their app. I've worked hard to make it easy for tools to live elsewhere and have no (or precious few) ties to VelocityTools' release schedule. That way the tools can stay in sync with the APIs that they front. Given that and the fact that we're already supporting other view technologies in Tiles, i think it would fit best here. I will, of course, help out with that as much as possible. Now, i realize that Sergey's code is for VelocityTools 1.x, but i do think we should target VelocityTools 2. Tools 2.0-beta2 should be out next week, and i don't intend for 2.0 GA to be far behind. Also, given the flexibility of Tools 2, it actually is pretty easy to have a 1.x compatible version extend the 2.x version. What do you think? > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
