Because of the conflict with the GPL and EPL, all EPL code in Ext GWT has been removed. This mainly impacts the Viewer implementation.
Ext GWT was already moving away from the Viewer code, in favor of the Ext based Store and new data loading API. The store and data loading API now support all features lost with the viewer code. Store supports StoreSorter, StoreFilter, and remote data loading. Also, Store is now an abstract base class with specialized ListStore and TreeStore subclasses.
There is a new branch in SVN that contains the new code for beta 3. For SVN users, it can be found at http://code.extjs.com/svn/gxt/branches/beta3. However, the code is not fully functional at this time. We recommend waiting for beta3 before moving to the new code. The branch will be brought back to the trunk when beta 3 is released. We have been working around the clock to get these changes implemented and hope to have beta 3 out by Monday.
We have started adding content to the wiki for Ext GWT. There is a new document covering the new data loading and store API. This document walks through the data loading, store, and binder classes. There will be more documents to follow.
We apologize for the API changes, but the EPL code had to be removed. Also, the Fx package has been updated to use the GWT 1.5 Animation class. The Moo Tools based code has been removed. With these changes, the Ext GWT library does not use code based on any third party code or libraries.
If anyone has any questions or comments, feel free to reply to this post.
It is only a violation if you distribute your code. However, this is no longer an issue as the EPL code has been removed.
Darrell, I would appreciate a response on this at the earliest. I've been told stop evaluating Ext GWT till the violations have been corrected as technically we shouldn't even be downloading a product that has a known license violation.
No, license changes are not retroactive.
Does this issue have an impact on the use of 0.5.2 for a commercial usage?
Unfortunately, the API had to be changed. We are very happy with the new design and believe you find it easy to use and less complex than the viewer code.
Any update? I'm afraid that the API is going to change again due to this issue and don't want to spend a lot of time refactoring my code.