That's fine, I just think we should have an agreed-upon, documented strategy for Struts users and developers. Doing an 'svn move' is pretty easy - creating a migration strategy, documenting it, writing tests to ensure the transition goes smoothly, keeping on top of bugs, etc, there are the tricky bits. Of course, being open source, I'd be happy for 3 out of the 4 :)
Don On Sun, Dec 21, 2008 at 11:35 PM, James Holmes <ja...@jamesholmes.com> wrote: > In my opinion the Java-tags should ultimately become the default in say 2.2 > or 2.3, but for now they should be a "supported, experimental" plugin > packaged with core. I say that because I think it's a little early to have > them replace the time-tested FreeMarker-based tags. If we can get them out > in the wild in 2.1 and people start using them, we can work out the kinks > and then make them the default. > > Perhaps the FreeMarker-based tags ultimately move to the Sandbox?? > > On Sun, Dec 21, 2008 at 7:29 AM, Don Brown <mr...@twdata.org> wrote: > >> Neat, I'm glad to see work finally being done on the tags. What >> exactly would this mean for 2.1 and 2.2? Would this be the default >> template engine for the tags? Will the documentation need to be >> rewritten? How do we keep the engines in sync if we keep the >> freemarker and velocity engines around? Do we have any tests for >> that? >> >> Don >> >> On Sun, Dec 21, 2008 at 5:24 AM, Musachy Barroso <musa...@gmail.com> >> wrote: >> > As mentioned on the other thread I's like to propose to move the java >> > tags out of the sandbox into the core plugins bundled with the >> > distribution, so they will be part of the 2.1 release. >> > >> > here is +1 >> > >> > musachy >> > -- >> > "Hey you! Would you help me to carry the stone?" Pink Floyd >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> > For additional commands, e-mail: dev-h...@struts.apache.org >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
