On 30 oct, 18:12, Sultan <[EMAIL PROTECTED]> wrote:
> Hello.
> Upgrading from 1.4.60 to 1.5.3 I can see the following compiler output
> difference. I have a module (let's name it ChildModule) that inherits
> from another module (let's name it ParentModule). ChildModule has some
> files in its public folder named the same as files in public folder of
> the ParentModule. This way the ChildModule "overrides" some static
> content of its ParentModule.
> When I compile with 1.4.60 the result is as expected and the output
> contains overriding files from ChildModule rather than overridden
> files from ParentModule.
> But when I compile with 1.5.3 the result is the opposite -- it
> contains files from ParentModule.
> This certainly looks like a regression to me but could it be as-
> expected behavior? Something introduced or caused by the "new Linking
> Subsystem"?
I don't know, but if it's been introduced somewhere, I'd rather say by
the new "Ant-like patterns":
http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&t=DevGuidePublicPackageFiltering
> Most importantly, what's the right way or work-around to achieve
> 1.4.60's result with 1.5.3?
If I read/understood the code correctly, resources earlier in the
classpath take precedence (that is, nothing to do with module
inheritance).
I don't know what the 1.4.60's expected behavior was, but for 1.5,
check your classpath.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
