[gwt-contrib] Re: I am getting ClassCastException on my app production code, but not on dev mode.
On Wednesday, February 12, 2014 2:09:41 AM UTC+1, James Nelson wrote: Please post to http://stackoverflow.com to get support; …or https://groups.google.com/d/forum/google-web-toolkit -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Not able to run GWTTestCase
Hello, I set up my Eclipse to contribute to GWT and worked through the Readme to set up an Eclipse workspace. All errors are gone in my Eclipse (Springsource Toolsuite) now, but I'm not able to run any GWTTestCase from within my Eclipse. The Ant build runs successfully. When trying to run any GWTTestCase I get this error: java.lang.Error: Unresolved compilation problems: The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved The import org.eclipse.jetty cannot be resolved AbstractLifeCycle cannot be resolved to a type RequestLog cannot be resolved to a type Request cannot be resolved to a type Response cannot be resolved to a type AbstractHttpConnection cannot be resolved to a type HttpFields cannot be resolved to a type Field cannot be resolved to a type Logger cannot be resolved to a type Logger cannot be resolved to a type Server cannot be resolved to a type WebAppContext cannot be resolved to a type Server cannot be resolved to a type WebAppContext cannot be resolved to a type Server cannot be resolved to a type WebAppContext cannot be resolved to a type Log cannot be resolved WebAppContext cannot be resolved to a type Server cannot be resolved to a type WebAppContext cannot be resolved to a type Server cannot be resolved to a type Log cannot be resolved Log cannot be resolved Server cannot be resolved to a type Server cannot be resolved to a type Log cannot be resolved WebAppContext cannot be resolved to a type WebAppClassLoader cannot be resolved to a type The method findResource(String) of type JettyLauncher.WebAppContextWithReload.WebAppClassLoaderExtension must override or implement a supertype method WebAppClassLoader cannot be resolved to a type WebAppClassLoader cannot be resolved to a type The method findClass(String) of type JettyLauncher.WebAppContextWithReload.WebAppClassLoaderExtension must override or implement a supertype method WebAppClassLoader cannot be resolved to a type The method isServerClass(String) is undefined for the type JettyLauncher.WebAppContextWithReload.WebAppClassLoaderExtension WebAppClassLoader cannot be resolved to a type The method addClassPath(String) is undefined for the type JettyLauncher.WebAppContextWithReload.WebAppClassLoaderExtension The method getInitParams() is undefined for the type JettyLauncher.WebAppContextWithReload The method setParentLoaderPriority(boolean) is undefined for the type JettyLauncher.WebAppContextWithReload The method isSystemClass(String) of type JettyLauncher.WebAppContextWithReload must override or implement a supertype method WebAppContext cannot be resolved to a type The method doStart() of type JettyLauncher.WebAppContextWithReload must override or implement a supertype method The method setClassLoader(JettyLauncher.WebAppContextWithReload.WebAppClassLoaderExtension) is undefined for the type JettyLauncher.WebAppContextWithReload WebAppContext cannot be resolved to a type The method doStop() of type JettyLauncher.WebAppContextWithReload must override or implement a supertype method WebAppContext cannot be resolved to a type The method getClassLoader() is undefined for the type JettyLauncher.WebAppContextWithReload The method setClassLoader(null) is undefined for the type JettyLauncher.WebAppContextWithReload AbstractConnector cannot be resolved to a type Log cannot be resolved Server cannot be resolved to a type Server cannot be resolved to a type AbstractConnector cannot be resolved to a type The method getConnector(TreeLogger) from the type JettyLauncher refers to the missing type AbstractConnector WebAppContext cannot be resolved to a type The method createWebAppContext(TreeLogger, File) from the type JettyLauncher refers to the missing type WebAppContext RequestLogHandler cannot be resolved to a type RequestLogHandler cannot be resolved to a type Log cannot be resolved Server cannot be resolved to a type WebAppContext cannot be resolved to a type WebAppContext cannot be resolved to a type AbstractConnector cannot be resolved to a type SslSocketConnector cannot be resolved to a type SslSocketConnector cannot be resolved to a type SelectChannelConnector cannot be resolved to a type at com.google.gwt.dev.shell.jetty.JettyLauncher.init(JettyLauncher.java:27) at com.google.gwt.junit.JUnitShell$MyJettyLauncher.init(JUnitShell.java:580) at
[gwt-contrib] Problem deploying GWT+Maven+Spring War on tomcat 6
Hello, I developed a GWT+Spring+Maven application on eclipse helios and all works well on eclipse. I clean, compile and install the application without any problem. But when deploy the generated war file on tomcat 6, deployment is successful, but the application doesn't start. Here is the error I get on the tomcat application manager: ECHEC - L'application pour le chemin de contexte /test1 n'a pas pu être démarrée and here is the tomcat6-stderr.log file: 2014-02-12 11:35:19 Commons Daemon procrun stderr initialized 12 févr. 2014 11:35:20 org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.29 using APR version 1.4.8. 12 févr. 2014 11:35:20 org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. 12 févr. 2014 11:35:22 org.apache.catalina.core.AprLifecycleListener initializeSSL INFO: OpenSSL successfully initialized with version OpenSSL 1.0.1e 11 Feb 2013 12 févr. 2014 11:35:27 org.apache.coyote.http11.Http11AprProtocol init INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 12 févr. 2014 11:35:27 org.apache.coyote.ajp.AjpAprProtocol init INFO: Initializing Coyote AJP/1.3 on ajp-8009 12 févr. 2014 11:35:27 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 7241 ms 12 févr. 2014 11:35:29 org.apache.catalina.core.StandardService start INFO: Démarrage du service Catalina 12 févr. 2014 11:35:29 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.39 12 févr. 2014 11:35:29 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Déploiement du descripteur de configuration host-manager.xml 12 févr. 2014 11:35:31 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Déploiement du descripteur de configuration manager.xml 12 févr. 2014 11:35:31 org.apache.catalina.startup.HostConfig deployWAR INFO: Déploiement de l'archive eskul.war de l'application web 12 févr. 2014 11:35:32 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:35:32 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/eskul] suite aux erreurs précédentes 12 févr. 2014 11:35:33 org.apache.catalina.startup.HostConfig deployWAR INFO: Déploiement de l'archive gwtspring.war de l'application web 12 févr. 2014 11:35:33 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:35:33 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/gwtspring] suite aux erreurs précédentes 12 févr. 2014 11:35:33 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire docs de l'application web 12 févr. 2014 11:35:33 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire examples de l'application web 12 févr. 2014 11:35:35 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire gwt de l'application web 12 févr. 2014 11:35:35 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:35:35 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/gwt] suite aux erreurs précédentes 12 févr. 2014 11:35:35 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire OLD de l'application web 12 févr. 2014 11:35:35 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire ROOT de l'application web 12 févr. 2014 11:35:35 org.apache.coyote.http11.Http11AprProtocol start INFO: Démarrage de Coyote HTTP/1.1 sur http-8080 12 févr. 2014 11:35:35 org.apache.coyote.ajp.AjpAprProtocol start INFO: Starting Coyote AJP/1.3 on ajp-8009 12 févr. 2014 11:35:35 org.apache.catalina.startup.Catalina start INFO: Server startup in 8253 ms 12 févr. 2014 11:38:10 org.apache.catalina.startup.HostConfig deployWAR INFO: Déploiement de l'archive gwtspring-0.0.1-SNAPSHOT.war de l'application web 12 févr. 2014 11:38:10 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:38:10 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/gwtspring-0.0.1-SNAPSHOT] suite aux erreurs précédentes 12 févr. 2014 11:38:33 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:38:33 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/gwtspring-0.0.1-SNAPSHOT] suite aux erreurs précédentes 12 févr. 2014 11:39:28 org.apache.catalina.startup.HostConfig deployWAR INFO: Déploiement de l'archive test1.war de l'application web 12 févr. 2014 11:39:29 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:39:29 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/test1] suite aux erreurs précédentes 12 févr. 2014 11:39:38
[gwt-contrib] Re: Problem deploying GWT+Maven+Spring War on tomcat 6
Please use https://groups.google.com/d/forum/google-web-toolkit or stackoverflow.com to ask for help. On Wednesday, February 12, 2014 3:36:11 PM UTC+1, efsiken wrote: Hello, I developed a GWT+Spring+Maven application on eclipse helios and all works well on eclipse. I clean, compile and install the application without any problem. But when deploy the generated war file on tomcat 6, deployment is successful, but the application doesn't start. Here is the error I get on the tomcat application manager: ECHEC - L'application pour le chemin de contexte /test1 n'a pas pu être démarrée and here is the tomcat6-stderr.log file: 2014-02-12 11:35:19 Commons Daemon procrun stderr initialized 12 févr. 2014 11:35:20 org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.29 using APR version 1.4.8. 12 févr. 2014 11:35:20 org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. 12 févr. 2014 11:35:22 org.apache.catalina.core.AprLifecycleListener initializeSSL INFO: OpenSSL successfully initialized with version OpenSSL 1.0.1e 11 Feb 2013 12 févr. 2014 11:35:27 org.apache.coyote.http11.Http11AprProtocol init INFO: Initialisation de Coyote HTTP/1.1 sur http-8080 12 févr. 2014 11:35:27 org.apache.coyote.ajp.AjpAprProtocol init INFO: Initializing Coyote AJP/1.3 on ajp-8009 12 févr. 2014 11:35:27 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 7241 ms 12 févr. 2014 11:35:29 org.apache.catalina.core.StandardService start INFO: Démarrage du service Catalina 12 févr. 2014 11:35:29 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.39 12 févr. 2014 11:35:29 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Déploiement du descripteur de configuration host-manager.xml 12 févr. 2014 11:35:31 org.apache.catalina.startup.HostConfig deployDescriptor INFO: Déploiement du descripteur de configuration manager.xml 12 févr. 2014 11:35:31 org.apache.catalina.startup.HostConfig deployWAR INFO: Déploiement de l'archive eskul.war de l'application web 12 févr. 2014 11:35:32 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:35:32 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/eskul] suite aux erreurs précédentes 12 févr. 2014 11:35:33 org.apache.catalina.startup.HostConfig deployWAR INFO: Déploiement de l'archive gwtspring.war de l'application web 12 févr. 2014 11:35:33 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:35:33 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/gwtspring] suite aux erreurs précédentes 12 févr. 2014 11:35:33 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire docs de l'application web 12 févr. 2014 11:35:33 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire examples de l'application web 12 févr. 2014 11:35:35 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire gwt de l'application web 12 févr. 2014 11:35:35 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:35:35 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/gwt] suite aux erreurs précédentes 12 févr. 2014 11:35:35 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire OLD de l'application web 12 févr. 2014 11:35:35 org.apache.catalina.startup.HostConfig deployDirectory INFO: Déploiement du répertoire ROOT de l'application web 12 févr. 2014 11:35:35 org.apache.coyote.http11.Http11AprProtocol start INFO: Démarrage de Coyote HTTP/1.1 sur http-8080 12 févr. 2014 11:35:35 org.apache.coyote.ajp.AjpAprProtocol start INFO: Starting Coyote AJP/1.3 on ajp-8009 12 févr. 2014 11:35:35 org.apache.catalina.startup.Catalina start INFO: Server startup in 8253 ms 12 févr. 2014 11:38:10 org.apache.catalina.startup.HostConfig deployWAR INFO: Déploiement de l'archive gwtspring-0.0.1-SNAPSHOT.war de l'application web 12 févr. 2014 11:38:10 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:38:10 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/gwtspring-0.0.1-SNAPSHOT] suite aux erreurs précédentes 12 févr. 2014 11:38:33 org.apache.catalina.core.StandardContext start GRAVE: Error listenerStart 12 févr. 2014 11:38:33 org.apache.catalina.core.StandardContext start GRAVE: Erreur de démarrage du contexte [/gwtspring-0.0.1-SNAPSHOT] suite aux erreurs précédentes 12 févr. 2014 11:39:28 org.apache.catalina.startup.HostConfig deployWAR INFO: Déploiement de l'archive test1.war de l'application web 12 févr.
[gwt-contrib] GWT Patch Review Policy Maintainer list
Hi Folks, One of the problems with patch reviews is that we don't have a guideline on who reviews patches and how does a patch get final approval. We put together a proposal for patch reviews, and a list of maintainers for GWT. At the SC meeting this morning, we decided this makes sense and will be moving forward with it. The two relevant documents are here: Patch Review Policy: https://docs.google.com/document/d/1_dBGeyqwMaLVXZ48VkOWz64bdLBdUeQgsvY8PEcXyMU/edit# Maintainer List: https://docs.google.com/document/d/1vyncxfuujIJ3L-PBLNM68tfeXRFZ4qDdnWEodblmvRg/edit#heading=h.3v5wd93k00oh We hope this will help streamline GWT contributions and make the process more efficient. Over time, we hope this will encourage contributors to take ownership and make substantial contributions. If you have GWT experience and would like to be a maintainer, please send email to one of Steering Committee members. Thanks, Bhaskar (On behalf of the GWT Steering Committee) -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] One time whitespace cleanup.
I'm going to do a one time automated whitespace cleanup of the GWT codebase. If you have a large (1000+ line) code review in progress, let me know and I'll hold off for a day or two to avoid conflicts. You can ignore whitespace changes in blame with git blame -w. John -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] One time whitespace cleanup.
I have plenty of patches that were waiting for apichecker. Can you hold of until next week? On Wed, Feb 12, 2014 at 12:35 PM, John Stalcup stal...@google.com wrote: I'm going to do a one time automated whitespace cleanup of the GWT codebase. If you have a large (1000+ line) code review in progress, let me know and I'll hold off for a day or two to avoid conflicts. You can ignore whitespace changes in blame with git blame -w. John -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] One time whitespace cleanup.
sure On Wed, Feb 12, 2014 at 6:07 PM, Goktug Gokdogan gok...@google.com wrote: I have plenty of patches that were waiting for apichecker. Can you hold of until next week? On Wed, Feb 12, 2014 at 12:35 PM, John Stalcup stal...@google.com wrote: I'm going to do a one time automated whitespace cleanup of the GWT codebase. If you have a large (1000+ line) code review in progress, let me know and I'll hold off for a day or two to avoid conflicts. You can ignore whitespace changes in blame with git blame -w. John -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] One time whitespace cleanup.
api-checker is in! On Wed, Feb 12, 2014 at 6:07 PM, Goktug Gokdogan gok...@google.com wrote: I have plenty of patches that were waiting for apichecker. Can you hold of until next week? On Wed, Feb 12, 2014 at 12:35 PM, John Stalcup stal...@google.com wrote: I'm going to do a one time automated whitespace cleanup of the GWT codebase. If you have a large (1000+ line) code review in progress, let me know and I'll hold off for a day or two to avoid conflicts. You can ignore whitespace changes in blame with git blame -w. John -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] One time whitespace cleanup.
Actually, there are still some changes that is not pulled in so I still cannot export my branches. On Wed, Feb 12, 2014 at 6:50 PM, Roberto Lublinerman rlu...@google.comwrote: api-checker is in! On Wed, Feb 12, 2014 at 6:07 PM, Goktug Gokdogan gok...@google.comwrote: I have plenty of patches that were waiting for apichecker. Can you hold of until next week? On Wed, Feb 12, 2014 at 12:35 PM, John Stalcup stal...@google.comwrote: I'm going to do a one time automated whitespace cleanup of the GWT codebase. If you have a large (1000+ line) code review in progress, let me know and I'll hold off for a day or two to avoid conflicts. You can ignore whitespace changes in blame with git blame -w. John -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com . For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
