source fully qualified. Thats nice if you always have your source in
the same place. You could try using the linked variables but then
thats also work. Do not see this as a real option for projects that
Donald W. Long (
> If that doesn't work, you could set the output directory of your
> dependencies to be the GWT output folder.
>
> jason
>
> On Mon, Jul 20, 2009 at 12:14 PM, martinhansen <
>
>
>
>
martin.hanse...@googlemail.com> wrote:
>
> > Hello Sean,
>
> > thank you very much. I've thought of that solution too, but it is not
> > appropriate for my GWT project. I have to add 4 external projects to
> > my GWT project, and all of these 4 projects are subject to change
> > every day. It would be too much work to export them to a jar file
> > every day. Is there some way to automatically add the external project
> > sources to the GWT output folder?
>
> > On 20 Jul., 18:03, Sean <
slough...@gmail.com> wrote:
> > > You can export the non-GWT java files into a jar and drop those in the
> > > WEB-INF/lib folder. That's what I do.
>
> > > On Jul 20, 11:44 am, martinhansen <
martin.hanse...@googlemail.com>
> > > wrote:
>
> > > > Hello,
>
> > > > my GWT server-side code needs an external java project. I have added
> > > > the project under "Configure build path / Projects". It works fine in
> > > > hosted mode. But when I deploy my application on a server, I get lots
> > > > of ClassNotFoundExceptions. Obviously, GWT cannot find the external
> > > > java code. When I look at the war\WEB-INF\classes folder, I see that
> > > > the external java classes have not been included.
>