Re: Hello Noob question

2024-03-12 Thread 'Tim Macpherson' via GWT Users
On the other hand gwt polymer is unmaintained for 6 years. Also it draws in elemental, which is nowadays replaced by elemental2. The 2 dependencies didn't cause problems previously but maybe someone else can advise. Yahoo Mail: Search, Organize, Conquer On Tue, Mar 12, 2024 at 23:20, Vijay

Re: Hello Noob question

2024-03-12 Thread Vijay Kishen Hampapur
Thanks , I figured out that the parent webapp didnt have the dependency called out. Followed by resources of the .nocache.js not being part of the jetty xml. Fixed and working now Thanks On Tue, Mar 12, 2024 at 9:02 AM 'tim_mac...@yahoo.co.uk' via GWT Users wrote: > > I am hoping to continue

Re: Hello Noob question

2024-03-12 Thread 'tim_mac...@yahoo.co.uk' via GWT Users
I am hoping to continue using this with upgrade to gwt 2.11.0 , gwt-maven-plugin 1.1.0 , java source level 11. I checked it as far as calling Polymer.startLoading() Polymer.importHref( .. ) No errors so far. in module.gwt.xml I presume you have: did you add the dependency in the

Hello Noob question

2024-03-12 Thread Vijay H
Created a starter using the modular-webapp archetype, and am trying to change the client module to use polymer elements and running into these sort of errors. Before I debug too far wanted to check if this is something that is doable or even recommended. This is for a class project. > Loading