Bryan Robbins

Whatever does get implemented here needs to conform to what was done in #247.

Have heard of this need from multiple projects. The normal approach of excluding Selenium Server from our Maven dependency doesn't work, as there are some non-compatible changes.

I agree with you, @SonOfFlyingPig. Maybe consider re-opening this one? Edit: Obviously it's already open (was looking at the "referenced issue" message above).

Any updates on this? For testing, have we confirmed whether will we need browser-specific tests that leverage a feature from the profile, or can we do in a browser-agnostic way?

CCB feedback, We need to check if WebDriver supports calling profile without binary. @SMxJrz is saying that as of 2012, binary was indeed required for this, but maybe this has...

This is more in support of future development than the current code. Agree that the current codebase does not really need splitting, but as we add widget libraries for various...

http://www.gwtproject.org/doc/latest/RefWidgetGallery.html

Sample app with all widgets: http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCheckBox Source: https://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/showcase/

mvn archetype:generate -DarchetypeGroupId=org.codehaus.mojo -DarchetypeArtifactId=gwt-maven-plugin -DarchetypeVersion=2.6.1 Creates empty GWT app. Can move app source from above comment into this structure.

Note: this feature will only work with XPath locators.