Thanks that does work but is still a maintainance issue if subsequent
Lift releases add new strings. I suppose I want to selectively
override individual strings and if not then fall back to lift-core
resource bundle.
-- Ewan
On Aug 11, 11:53 am, "marius d." wrote:
> You can specify your own ResourceBundle for Lift's strings:
>
> LiftRules.liftCoreResourceName which is currently set to "i18n.lift-
> core"
>
> or you can manually change lift-core.properties files from the Lift's
> jar file.
>
> Current Lift's strings are in lift\src\main\resources\i18n\lift-
> core.properties
>
> Br's,
> Marius
>
> On Aug 11, 1:13 pm, Ewan wrote:
>
>
>
> > There are a couple of cases where I would like to override the
> > localised messages that Lift itself users such as S.notice(S.??
> > ("logged.in")) in MetaMegaProtoUser.login(). I was hoping I could
> > override by popping the name=value in my message bundle properties
> > file but it does not work. I realise I could override/copy
> > MetaMegaProtoUser.login() and replace that one line with a key from my
> > own bundle but I am not a fan of copy/paste inheritance. Would you
> > accept a request to change S.notice(S.??("logged.in")) etc to call
> > functions we can override?
>
> > -- Ewan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---
