Re: [Bodington-developers] i18n template compilation problem

[Alistair Y. <ali...@sm...>]

> Au contraire! I apologize for the somewhat sarcastic tone of some of 
> my previous posts
phew, I thought you hated me! I'm very delicate you know.

when I say template compilation is boken I don't really mean it's 
broken - they compile fine. It's just that the resource files won't be 
found. I'm moving the resource files to the classpath which will remove 
this issue. It won't, however, remove the problem of a user moving the 
webapp around but the templates would break if they did that, whether 
they were precompiled or compiled by bod.

perhaps a FAQ entry on how to move bod to a new server/webapp root? 
first thing after moving is to delete the compiled templates.

> It's just that it strikes me you should be discovering some of these 
> issues *before* committing rather than after
yes, I agree. I'm just using the space between now and 2.6 to get as 
much in head as I can, without major merging, which I can't do as I 
have a multitude of other projects waiting to bite my bum ;) If I get 
any more curmudgeonly I'll be getting dragged behind the boat in my own 
dinghy.

Alistair


On 24 May 2005, at 15:29, Alexis O'Connor wrote:

> Alistair Young wrote:
>> I know i18n is an unpopular subject and it's seen as superfluous by 
>> some people, especially trying to retrofit it to an ancient system 
>> like this - if it's too much for some to bear I can always just stop?
>
> Au contraire! I apologize for the somewhat sarcastic tone of some of 
> my previous posts, but I'm actually entirely sympathetic to the notion 
> of being i18n compatible. It's just that it strikes me you should be 
> discovering some of these issues *before* committing rather than 
> after.
>
> Just as a general point of illumination, the template-compiler ANT 
> task (org.bodington.ant.TemplateBuilderTask) now supports the boolean 
> 'failonerror' attribute (making it more consistent with complementary 
> tasks such as Javac and JspC). By default this is true. Therefore, 
> where a broken template is template no. 300 of 500, the following 199 
> are not even looked at. The whole build will fail as soon as a 
> template contains 'unrecoverable errors'. Setting failonerror to 
> 'false' means the build continues. If any templates contain 
> unrecoverable errors then a warning message is written to the console 
> saying how many fell into this category.
>
>
> Alexis
>
>
> P.S. Of course, the other alternative as the task is now an implicit 
> FileSet is to do something like the following :-)
>
> <template-compiler ... >
> 	<include name="**/*.html" />
> 	<exclude name="**/templateGivingYouAgro.html" />
> </template-compiler>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Yahoo.
> Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
> Search APIs Find out how you can build Yahoo! directly into your own
> Applications - visit 
> http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers