Re: Module Inheritance and path excludes
Just as the "excludes" seems to be too powerful and exclude the files *everywhere*, regardless of the inheritance topology, the "skips" seems to be* too weak*. In my tests, if I convert the *Excluder* Module to use skips, it appears to do *nothing* when included by Module *B* as I described above - the resources are still there in the WAR. Note that in my design, Module *A* picks up the resources via a dependency on Module* ImageResources*, where* A* and* ImageResources* may not even have the same (Java) package/path. I then want to define Module* B* as inheriting* A* and *Excluder*, and have *Excluder* exclude those resources. Using "skips" this fails - *Excluder* does nothing. What I need is a way to delete file resources from a module that were picked up by it inheriting another module, without losing the capability to have a third module add them back after inheriting the first. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Module Inheritance and path excludes
I think all includes and excludes rules are merged before evaluated. So if something is excluded anywhere it is gone for all modules, you can not get it back. I think the "skips" attribute/tag is more what you want. It lets you ignore files just for a single module while other modules might still need these files. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Module Inheritance and path excludes
Suppose we define a GWT Module *ImageResources* that includes certain resources in its default public directory, and then we define a Module *Excluder* that specifically excludes those resources via something like: Then we can define a Module* A* that includes the resources via: : (stuff) : and another Module *B* that's just like *A* except it excludes those same resources via: That is, in the WAR file created by GWT compile for Module *B*, the files under imageResources will be missing. (This works.) -- Now the problem. I want to allow a Module* C* to be defined as such: but it doesn't appear to work. That is, although *B* is derived from *A* by removing certain resources, I want to allow them to be added back by an overriding inherits declaration. (Note that we're inheriting B, so overriding that decision at the "closer" local level seems logically plausible.) Is there a fix? Of course, another solution is to move the "meat" from Module *A*'s definition into Module *B* so that we never need to use *Excluder*, but that's not the solution I was hoping for. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
