Thanks. That is an interesting thread, although it seems to be
addressing a separate need: multiple classpath definitions, which I
think would be a big win for the GEP.

I've been using multiple classpath definitions in my Ant build scripts
for years. Usually there's a runtime classpath with JDBC drivers,
maybe something from Apache Commons, and anything else I need to
deploy. There's also a dev classpath which includes everything on the
runtime classpath, plus libs that are only used during development or
are known to be provided by the app server (the core J2EE lib, for
example). This dev classpath has things that I need in order to
compile, test, etc., but that will not ultimately be deployed with the
app. With GWT applications, the dev classpath will also include any
client-only libraries (e.g., gwt-incubator.jar). Having all of this in
one classpath definition causes GEP to generate warnings. There's an
"ignore the fact that this won't be available on the server" feature
in GEP to remove these warnings, but I think turning that into a more
explicit runtime vs. dev configuration would be beneficial. Solving
the source control issue is then pretty simple: the plugin would copy
all static content, GWT compiler output, and anything on the runtime
classpath into a configurable exploded webapp dir where either the
bundled Jetty or an external ("-noserver") app server can serve the
app. I can check into source control any libraries that I choose and
reference the others as Eclipse libraries, classpath variables, etc.



On Sat, Apr 25, 2009 at 10:45 PM, Allen Firstenberg <[email protected]> wrote:
>
> There has also been some similar discussion in this thread:
> http://groups.google.com/group/google-appengine-java/browse_thread/thread/67cb7cdaefc8429f?tvc=2
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to