2008/6/28 Nathan Bubna <[EMAIL PROTECTED]>: > 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.
In fact I was thinking of a separate optional JAR, just like the "tiles-jsp.jar". Is it possible? > 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. OK, remember that you are a PMC member of Tiles, too ;-) > 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. +1 to use Tools 2, independently from your release schedule. > Also, > given the flexibility of Tools 2, it actually is pretty easy to have a > 1.x compatible version extend the 2.x version. I think that retrocompatibility depends on volunteers effort: if someone of us really *wants* to use Tools 1, then OK. > What do you think? I think we have left one important point: the codebase of the work made by Sergey lives outside of Apache, so probably an IP clearance process is necessary. Sergey, if you still want to contribute, do you simply want to donate your code (with obvious recognition in SVN logs and contributor page), or do you want to collaborate to create a Tiles 2 + VelocityTools 2 module? Either way, your contribute will really be appreciated :-) Thanks Antonio
