Hi all,
Thanks for the suggestions so far.
In our project.gwt.xml the sources look like this:
<source path='client' />
<source path='shared' />
Although our deploy does not contain our compiled test classes, gwt
designer also interprets test classes as part of the project and tries
to compile them (they have the same classpath). I renamed the test
package to another package and this worked. Note however that this is
just a workaround, because we would like the test package to have the
same package (to be able to use protected fields and methods).
Alan: this is exactly what we mean. We cannot startup the GWT designer
because it raises up all sorts of errors not finding any classes which
are never used client-side.
Eric: I found the "check for client classpath" but it is not on, so I
cannot turn it off ;)
Eric: you say the the GWT designer does not compile anything. Well, I
get loads of compile errors (because it tries to compile the client
and shared packages), so how can you explain that?
Thanks,
Baloe
On 18 mei, 01:44, Eric Clayberg <clayb...@google.com> wrote:
> All you need is the full version of GWT Designer (not WB)...
>
> http://code.google.com/webtoolkit/tools/download-gwtdesigner-beta.html
>
> On May 17, 2:57 pm, Alan Chaney <a...@mechnicality.com> wrote:
>
>
>
>
>
>
>
> > On 5/17/2011 11:41 AM, Eric Clayberg wrote:> I woud suggest opening a bug
> > and including a complete test case that
> > > illustrates the exact problem you are having.
>
> > OK Eric I'll do that.
>
> > > You might also turning off the "WindowBuilder> GWT> Builder> Check
> > > for 'client' classpath" preference...
>
> > >http://code.google.com/webtoolkit/tools/gwtdesigner/preferences/gwt/p...
>
> > Sadly, I'm seeing this problem with Designer, and there doesn't seem to
> > be such an option. The implication here is that I need to install the
> > full Window Builder to be able to get around this problem?
>
> > Alan
>
> > > On May 17, 2:25 pm, Alan Chaney<a...@mechnicality.com> wrote:
> > >> On 5/17/2011 11:01 AM, David Chandler wrote:> How is the GWT compiler
> > >> able to compile your server-side classes? GWT
> > >>> Designer is correct to include any source dirs you've specified in
> > >>> your gwt.xml.
> > >> I raised a related issue the other day concerning this - GWT Designer
> > >> does not seem to correctly recognize the 'excludes' attributes.
>
> > >> In the case below, the OP could exclude. for example, **/*Test*.java in
> > >> the module file. Although this works fine for the actual GWT compiler,
> > >> GWT Designer chucks out (in my case) thousands of errors, all of them
> > >> related to it incorrectly finding references to things like
> > >> org.junit.Assert etc. I asked if this was a known bug, and it seems that
> > >> its not, so maybe I should report it?
>
> > >> Alan
>
> > >>> /dmc
> > >>> On Tue, May 17, 2011 at 1:34 PM, Baloe<nielsba...@gmail.com
> > >>> <mailto:nielsba...@gmail.com>> wrote:
> > >>> Hi all,
> > >>> Is there any way to restrict GWT Designer to only certain packages?
> > >>> We have a serieus problem with this right now. We have some entity
> > >>> classes (in the shared package) with annotations. These annotations
> > >>> are implemented server-side, and we cannot move the classes to the
> > >>> serverside because we also read/write the entity classes in the
> > >>> client
> > >>> package. But, GWT Designer also wants to compile these classes.
> > >>> Another thing that is happening right now is that GWT Designer
> > >>> starts
> > >>> also to compile our test package, which doesn't succeed because
> > >>> these
> > >>> classes can never be compiled at client-side.
> > >>> So, how do we restrict GWT Designer? Later on it will randomly
> > >>> chose
> > >>> to compile our server package as well, which means that we should
> > >>> put
> > >>> our /server package in another eclipse project ;)
> > >>> Thanks for any hints,
> > >>> Baloe
> > >>> --
> > >>> 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
> > >>> <mailto:google-web-toolkit@googlegroups.com>.
> > >>> To unsubscribe from this group, send email to
> > >>> google-web-toolkit+unsubscr...@googlegroups.com
> > >>> <mailto:google-web-toolkit%2bunsubscr...@googlegroups.com>.
> > >>> For more options, visit this group at
> > >>> http://groups.google.com/group/google-web-toolkit?hl=en.
> > >>> --
> > >>> David Chandler
> > >>> Developer Programs Engineer, Google Web Toolkit
> > >>> w:http://code.google.com/
> > >>> b:http://googlewebtoolkit.blogspot.com/
> > >>> t: @googledevtools
> > >>> --
> > >>> 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.
--
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.
