http://gwt-code-reviews.appspot.com/1503804/diff/1/user/src/com/google/web/bindery/requestfactory/apt/ValidationTool.java File user/src/com/google/web/bindery/requestfactory/apt/ValidationTool.java (right):
http://gwt-code-reviews.appspot.com/1503804/diff/1/user/src/com/google/web/bindery/requestfactory/apt/ValidationTool.java#newcode50 user/src/com/google/web/bindery/requestfactory/apt/ValidationTool.java:50: * output jar and the binary names of RequestFactory interfaces that should be Out of curiosity: why an output *jar* and not an output folder? (or giving the user the choice). Using a folder would allow outputting to a WAR's WEB-INF/classes (before packaging the WAR of course) or, when building using Maven, outputting to target/classes or target/generated-classes (whatever is best for Maven) so the generated classes can be used by tests (which are run before the code is packaged into a JAR, and adding a JAR to the classpath that is not a dependency might not be practical, if at all possible; it's late here, so I haven't checked how it could work). http://gwt-code-reviews.appspot.com/1503804/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
