Author: sco...@google.com
Date: Thu Dec 11 17:55:55 2008
New Revision: 4313
Modified:
wiki/WAR_Design_1_6.wiki
Log:
Updating open issues and tasks.
Modified: wiki/WAR_Design_1_6.wiki
==============================================================================
--- wiki/WAR_Design_1_6.wiki (original)
+++ wiki/WAR_Design_1_6.wiki Thu Dec 11 17:55:55 2008
@@ -120,19 +120,19 @@
Make sure that it expects to track the list of active modules for a given
project.
+== Deprecation Policy==
+
+The 1.6 release should deprecate the legacy entry points so that they may
be removed entirely in the subsequent release. Without a forcing function,
there is no incentive for users to migrate to newer entry-points, leaving
them as the proverbial albatross.
+
+== Misc ==
+ * JUnit will subclass GWTShell for now. We will revisit this in 2.0
with OOPHM.
+
== Open Issues ==
# How do we isolate the web app classloader to ensure same behavior in
deployment?
- # What happens to the GWT `<servlet>` tag for `HostedMode`?
- # Validate that web.xml matches and suggest the text to add?
# `war/qualified.ModuleName/scripts/` is likely to change in 2.0 with
runAsync
- # How will JUnit work?
- # Probably can use legacy stuff for now
# Will this design work with Maven?
-== Deprecation Policy==
-
-The 1.6 release should deprecate the legacy entry points so that they may
be removed entirely in the subsequent release. Without a forcing function,
there is no incentive for users to migrate to newer entry-points, leaving
them as the proverbial albatross.
-
== Open Tasks ==
# Make sure app creator and samples follow this structure.
- # Deprecate somehow GWTCompiler and GWTShell
\ No newline at end of file
+ # We need to parse the web.xml and verify that all module <servlet> tags
have been declared; if not we should warn and provide the correct text to
add.
+
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
