ANN: Eclipse-ified version of the GWT 1.1 samples

[Ed Burnette]

I imported all the GWT 1.1 samples into Eclipse, got them to build and
run, and zipped up the projects for your convenience. A download is
available here:

http://www.gwtpowered.org/downloads/samples/gwt-samples-1.1.0.zip

This was a bit tedious to do so hopefully a future version of GWT will
include the necessary files (.project, .classpath, and project.launch)
already in the package released by Google.

One difference from what the projectCreator/applicationCreator scripts
would do is that I've used Eclipse's user library feature to avoid
having hard coded paths in the projects (you could do the same thing
with classpath variables). To define user libraries in Eclipse, go to
Window > Preferences > Java > Build Path > User Libraries and create
one for "gwt-user" and one for "gwt-dev". Or just copy the xml below
into gwt-1.1.0.userlibraries, modify the paths to point to where you
installed GWT, and then import the file from that same Preferences
window.

gwt-1.1.0.userlibraries (watch out for line breaks):

--snip--
<?xml version="1.0" encoding="UTF-8"?>
<eclipse-userlibraries version="2">
<library name="gwt-dev" systemlibrary="false">
<archive path="C:/Program
Files/Google/gwt-windows-1.1.0/gwt-dev-windows.jar"/>
</library>
<library name="gwt-user" systemlibrary="false">
<archive path="C:/Program
Files/Google/gwt-windows-1.1.0/gwt-user.jar"/>
</library>
</eclipse-userlibraries>
--snip--

Everything in this post including the sample modifications is covered
by the Apache license.

Tested with Eclipse SDK 3.3M1.

Enjoy,
--Ed Burnette
Author, "Google Web Toolkit - Taking the pain out of Ajax",
www.pragmaticprogrammer.com

[br...@google.com]

Thanks, Ed!

Ed Burnette wrote:
> This was a bit tedious to do so hopefully a future version of GWT will
> include the necessary files (.project, .classpath, and project.launch)
> already in the package released by Google.

Our thought was to not play favorites since there are so many good IDEs
out there. Maybe we'll find a deployment structure that lets us include
project configs for several of the popular IDEs.

> One difference from what the projectCreator/applicationCreator scripts
> would do is that I've used Eclipse's user library feature to avoid
> having hard coded paths in the projects (you could do the same thing
> with classpath variables).

Great suggestion.

-- Bruce

[Ed Burnette]

Well, projectCreator/applicationCreator already take a -eclipse option
:). NetBeans has a way to import Eclipse projects. Not sure about IDEA
but they're building in a GWT wizard in 6.0 anyway.

[Konstantin Scheglov]

Ed Burnette wrote:

> Well, projectCreator/applicationCreator already take a -eclipse option
> :). NetBeans has a way to import Eclipse projects. Not sure about IDEA
> but they're building in a GWT wizard in 6.0 anyway.

Eclipse also has GWT project/module/service/etc wizards. ;-)

[patrick....@usa-spaceops.com]

I downloaded and expanded the zip file. In eclipse I imported the Hello
project. The gwt-user.jar file was unbounded. Did you copy this jar
file into the project directory (e.g: lib folder) OR somewhere else??

[Ed Burnette]

I designed my zip file with Eclipse user libraries. I know you have it
working since we corresponded in email but if somebody else is reading
this, Eclipse has a user library feature where you can associate a
logical library name like "gwt-dev" with a physical jar file like
"c:\program files\google\gwt-windows-1.1.0\gwt-dev-windows.jar". The
advantage is that all your projects can just reference the logical name
and you can change one place when a new version comes out to have all
your projects use the new version. It also lets you share projects with
people who installed GWT in a different place than you did.