Closed matoorn closed 9 years ago
GWT refactoring implies more things like change manually entry-point namespaces in .gwt.xml module and change module name in eclipse launchers etc.
I have double checked, and changing demo namespace works perfectly.
Yes, thank you, it is working fine now. It could have been my env. apologies for that.
On Fri, Jul 10, 2015 at 1:21 AM, Manuel Carrasco Moñino < notifications@github.com> wrote:
GWT refactoring implies more things like change manually entry-point namespaces in .gwt.xml module and change module name in eclipse launchers etc.
I have double checked, and changing demo namespace works perfectly.
— Reply to this email directly or view it on GitHub https://github.com/vaadin/gwt-polymer-elements/issues/41#issuecomment-120180237 .
Running the Sampler example in demo with eclipse is fine. However re-factoring and changing the package for the Demo.gwt.xml module from: com.vaadin.components.gwt.polymer to a different package such as: com.myproject.components.gwt.polymer will not run, with exceptions.