Hello to all! Sorry for such a delay in responce, was on vacation and had slow access to e-mail.
I just would like to summarize our thoughts. I agree with Tim, that a tool to generate Msg and MsgUtil classes based on the teamplate may has sence. I had doubts that these classes are ot be changed quite often to generate them every build time. Thus, idea to regenerate classes for all modules only when teamplate is changed seems to me more reasonable. I will work on it. As far as I understood we've chosen good old "non-Eclipse" method, hence I'm going to use Msg teamplate from the luni module. The one main problem that is still unresolved - how to get messages for internationalization from modules. Messages externalization utility in Eclipse can be used only for messages without arguments, that are fully situated on the line, otherwise they will be splitted into 2 separated messages. Also Eclipse utility doesn't know anything about arguments in messages. May be anyone has an idea how it is better to extract messages in the proper format? Thanks, Ilya. On 7/18/06, Tim Ellison <[EMAIL PROTECTED]> wrote:
Geir Magnusson Jr wrote: > I'm a little confused because I think Alexey combined two ideas that can > be treated separate, using eclipse technique, and using lightweight code > generation to create your solution automatically. > > I believe that you are rejecting the Eclipse solution as we don't have > the same resource message requirements that Eclipse does. Right? I'm not rejecting it, I just have no basis for an opinion. In such cases I would usually go with the common convention until we determine that there is a win elsewhere. > Separately from that, what do you think about the build-time code gen > (i.e. simple template w/ package name replacement...) so that it's easy > to modify and switch in the future? A simple tool to gen the code as a separate step would be ok. I'm not convinced that we need to generate it each time we build, the Msg and MsgUtils don't change frequently (same for the the Eclipse method if we go for that). I'd put the 'template' code and the code gen tool into our project tools directory, and run it when we update the template then check the generated code (with 'do not edit blah blah' comments) into SVN for each module. I see it being analogous to the javah process for the JNI calls. Regards, Tim -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK. --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- -- Ilya Okomin Intel Middleware Products Division
