Sunday, May 25, 2014

Re: Google Chrome 35 GWT plugin incompatibility

It is not an option for me. We are depending on jboss fuse/karaf to provide us with osgi bundle resolving. I can not just slap together a classpath and make it run in Jetty.
and the whole maven movement hasn't reached the company I work for (it is coming, but it takes time).



On Sat, May 24, 2014 at 12:38 AM, Thomas Broyer <t.broyer@gmail.com> wrote:
FYI, I just use the maven plugins for tomcat or jetty which run the classes right from my projects (automatically recompiled by my IDE) with automatic app reload (or just a keypress away).

See https://github.com/tbroyer/gwt-maven-archetypes for my setup.

On a project with heavy jetty customization, we just had a "dev" config for jetty to load classes from our project, with automatic app reload.
The same is available for tomcat.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment