On 2 nov, 21:41, Eric <[email protected]> wrote:
> The advice on the GWT testing page is to have your GWT module inherit
> from the JUnit module.
Where did you see that advice? I cannot find it on
http://code.google.com/webtoolkit/doc/1.6/DevGuideTesting.html
> However, you shouldn't deploy for production
> while still inheriting the JUnit module, because that forces you to
> include junit.jar in the war file.
1. you generally do not deploy your GWTTestCase (or other test-)
classes (notably due to the fact that you do not deploy your GWT code
as Java classes but compiled into JavaScript)
2. even if you do, you'll never reference them in your production
code, so you won't face the NoClassDefFoundError due to the absence of
junit.jar
> Should the advice on the testing
> page be to create a module inheriting JUnit and the production module?
JUnitShell will synthesize such a module (inheriting both your module –
as returned by your GWTTestCase's getModuleName()– and the JUnit
module). You do not have to explicitly inherit the JUnit module,
unless your GWTTestCase classes are in the classpath when you call the
GWT Compiler (which IMO is bad practice).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
