I wasn't including the source files. Disregard. Release should be
soon.
On Sep 17, 3:38 pm, "chris.ruffalo" <[EMAIL PROTECTED]> wrote:
> One final bit of help.
>
> I'm having problems building a jar that will work with the modules to
> compile under a normal project. If I export the jar with Eclipse
> everything works fine ("add directory entries" and all that) and the
> compile and shell modes work.
>
> If I use an ant task to build the jar then it will not work with the
> compiled mode or the shell mode.
>
> I've never been able to have ant (1.7.1) do this in the past either,
> on other projects.
>
> Any help would be appreciated.
>
> On Sep 12, 11:08 pm, "chris.ruffalo" <[EMAIL PROTECTED]> wrote:
>
> > I see. That worked, I guess I was expecting something bad to happen
> > if I didn't write new source. In retrospect why would that happen?
>
> > Fortunately I don't have to do anything different (per user agent)
> > yet.
>
> > On Sep 12, 3:39 pm, BobV <[EMAIL PROTECTED]> wrote:
>
> > > > Namely:
> > > > Hosted mode works fine but compiling tries to rebind twice (even
> > > > though I only have
> > > > one GWT.create()) and it can't create the printwriter because the
> > > > class it is trying to write
> > > > already exists. I guess I need a smarter generator. (?)
>
> > > This is expected behavior. The generator gets called once per
> > > permutation. If the PrintWriter is null, just return the name of the
> > > implementation class that you were tryping to create. It works this
> > > way because you may want to generate different code for different
> > > user.agent values or along some other deferred-binding axis. In this
> > > case, you would name the implementation classes differently.
>
> > > --
> > > Bob Vawter
> > > Google Web Toolkit Team
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
