Ok I understand why splitting client and server side might be a good idea and we will check if this is applicable for us and worth the time investment.
Except the Warnings/Errors in DevMode do we have to fear anything else when we keep up our approach with GWT 2.6? Why does this only come up with 2.6 and not with 2.5.1? Am Dienstag, 18. Februar 2014 15:22:32 UTC+1 schrieb Thomas Broyer: > > > > On Tuesday, February 18, 2014 2:15:26 PM UTC+1, Dennis R. wrote: >> >> Hi, >> >> we got a similiar problem in our project. At startup in DevMode we get: >> >> log4j:WARN No appenders could be found for logger >> (org.eclipse.jetty.util.log). >> log4j:WARN Please initialize the log4j system properly. >> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for >> more in >> >> And after that lots of errors like: >> >> log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable >> to a "org.apache.log4j.Appender" variable. >> log4j:ERROR The class "org.apache.log4j.Appender" was loaded by >> log4j:ERROR [sun.misc.Launcher$AppClassLoader@566d0085] whereas object of >> type >> log4j:ERROR "org.apache.log4j.ConsoleAppender" was loaded by >> [WebAppClassLoader=MyPortal (0.1)@61c42ccd]. >> >> This is only in DevMode and it seems to have no other effect then to be a >> little annoying but this was not the case with 2.5.1 so there seems to be >> something changed with the startup. This is why we don't know if it's safe >> for us to upgrade to 2.6.0 or not. >> >> I tried to move the log4j dependencie in Eclipse runconfig from User to >> Bootstrap but this seems not possible because we are using maven >> dependencies and our structure there now looks like: >> >> >> *Bootstrap Entries*- JRE System Library >> User Entries >> - main/src >> - main/resource >> - test/src >> - test/resource >> - *dependency*/main/src >> ... >> ... >> + MyPortal (default classpath) >> --- MyPortal (folder icon) >> --- Maven Dependencies (libs icon) >> --- GWT SDK 2.6 (libs icon) >> >> In this structure everything under +MyPortal is not openable. The >> dependency projects are also provided via the pom.xml as dependency and one >> of it is our domain model which should not be on the client. But if I >> understand the information in this thread correctly everything under "User >> Entries" is on the clients classpath instead (or both?) on the webapps >> classpath? >> > > Yes. > (the "instead of" bit depends on your project; I keep thinking that if you > mix client-side and server-side code in the same Maven module, then you're > doing it wrong; Maven wants you to modularize your project, and it really > works great; see https://github.com/tbroyer/gwt-maven-archetypes for > examples) > > >> Can you please provide us some information about the impact of this >> change in our case or how to fix this issue? >> > > If you insist using a single Maven module (I've heard it works better with > Google App Engine), then run "mvn package" once (and then again each time > you change your dependencies) so the server-side dependencies are copied > into target/…/WEB-INF/lib. > See > http://web.archive.org/web/20130619170526/https://developers.google.com/eclipse/docs/faq#gwt_with_maven > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
