You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Musachy Barroso <mu...@gmail.com> on 2009/10/27 18:22:30 UTC
Re: WW-3291. What should I do to help move this issue forward.
usually just wait until one of those lazy struts committers merge the
patch :). I can take a look at it and merge it into trunk on the
weekend.
On a separate note, now that Sitemesh is more modular and reusable, is
it possible to write some tests for it?
musachy
On Tue, Oct 27, 2009 at 10:13 AM, Christian Stone <xt...@stonescape.net> wrote:
> I am asking simply because I have other bug fixes in the same codebase, and
> I want to resolve one before I complete and build a patch for the other.
> However, I do not have a possibility of marking the bug resolved or to
> actually apply the patch to the codebase (I have not checked but I doubt I
> have write access to the struts source base). So what should I do now?
> What is the process? I reread the docs and there is nothing discussing on
> what to do after submitting a patch for an issue.
>
> Thanks much!
>
> -- Christian
>
> P.S. The new freemarker/velocity code is working great. I moved it to a
> production server to test and it has no problem mixing freemarker decorators
> on velocity/jsp results, vice versa... and handles both freemarker and
> velocity decorators just like SiteMesh intended.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Screw John Galt, who is Martin Gainty?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: WW-3291. What should I do to help move this issue forward.
Posted by Lukasz Lenart <lu...@googlemail.com>.
2009/10/27 Musachy Barroso <mu...@gmail.com>:
> usually just wait until one of those lazy struts committers merge the
> patch :). I can take a look at it and merge it into trunk on the
> weekend.
Lazy? I'm still a bit afraid to make a change into Struts2 code base ;-)
Regards
--
Lukasz
http://www.lenart.org.pl/
http://dailylog.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org