You are right! This was the problem! :))) I didn't know what the exclusion filter was and somehow it was added automatically during the development.
I removed it and now I can compile the module in both source folders. Thank You Rajeev, Nikolay On Sep 14, 4:54 pm, Rajeev Dayal <rda...@google.com> wrote: > Hey Nikolay, > I think that you may have an exclusion filter which is too aggressive on > your "target/base-resources" directory. It seems that you have an exclusion > filter of "**". Won't that match everything? > > Rajeev > > On Fri, Sep 11, 2009 at 4:17 PM, Nikolay <erdtekw...@googlemail.com> wrote: > > > Hi Rajeev, > > > yes, when I move the module XML file from the "src/main/java" into the > > "target/base-resources" directory it is not found by the compiler. > > > In the "target/base-resources" directory, the XML file is in package > > "A.B.C.D" (let's say), but in the Package Explorer the package is > > shown not on 1 line, but as a tree and the icons are like "open > > folders". > > > When I move the XML file in the "src/main/java" directory, the package > > "A.B.C.D" is shown on 1 line and the icons are like the normal java > > package icons - a brown quadrat divided into another 4 brown quadrats. > > > If this would help: > > <classpathentry kind="src" output="target/classes" path="src/main/ > > java"/> > > <classpathentry excluding="**" kind="src" output="target/classes" > > path="target/base-resources"/> > > > Greetings, > > Nikolay > > > On Sep 11, 9:42 pm, Rajeev Dayal <rda...@google.com> wrote: > > > Hi Nikolay, > > > Is the behavior reproducible? That is, if you move the module file back > > into > > > the other source directory, do you run into the problem? > > > > Rajeev > > > > On Fri, Sep 11, 2009 at 3:23 PM, Nikolay <erdtekw...@googlemail.com> > > wrote: > > > > > I moved the MyModule.gwt.xml file from the my "target/base-resources" > > > > source directory into the "src/main/java" source directory and it was > > > > recognized by the Compiler! :) > > > > > That was strange, because before that it worked in the "target/base- > > > > resources", but not in the "src/main/java" source directory. > > > > > On Sep 11, 7:24 pm, Nikolay <erdtekw...@googlemail.com> wrote: > > > > > Hello, > > > > > > I have project with Maven and GWT nature, and I use the GWT Compiler > > > > > (the red button in Eclipse). I have already defined MyModule.gwt.xml > > > > > and its needed classes and I can run my GWT Application under Hosted > > > > > Mode. > > > > > > However at some point of the development, when I tried to use the GWT > > > > > Compiler, it could not automatically find my module and I got the > > > > > message "Add an entry point module" in red. And this is how it is > > now. > > > > > Do you know what could be the problem? How the plugin searches for a > > > > > module and in what case it is not found? > > > > > > Additional Info: > > > > > Eclipse 3.5 > > > > > GWT 1.7 > > > > > GWT Plugin: 1.1.0.v200907291526 > > > > > com.google.gwt.eclipse.core.prefs contain "entryPointModules=" (i.e. > > > > > empty) > > > > > > Greetings, > > > > > Nikolay --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
