Thanks Rick for the valuable information. I do not like the idea of mixing jars from different versions just for svn's sake. For now I'll remove GAE SDK from svn and handle things manually which is a real pain. Hope they fix this issue soon.
On Thursday, March 1, 2012 3:25:39 PM UTC+1, Rick Mangi wrote: > > Dilbert, see my reply on the ticket. > > Max - that comment about svn being writable is nonsense. I wish you guys > would talk to your own support engineers. I tried that solution with my > premier support contact and it doesn't even make sense. svn directories are > always writable. This is a bug, it's reproducible and it's going to be > fixed in 1.6.4 (supposedly). The workaround is posted in my comment on the > ticket. It took me weeks of back and forth to get the google engineers to > see the problem. If someone had just tried it out I'm sure they would have > seen the problem right away. > > On Thursday, February 2, 2012 4:05:43 AM UTC-5, dilbert wrote: >> >> We keep the GAE sdk (together with the project) in svn. Yesterday we >> upgraded to GAE sdk 1.6.2. It worked fine until we checked it into the svn >> repo. After that when the server is started it dies with the following >> message: >> >> Exception in thread "main" java.lang.ExceptionInInitializerError >> at com.google.appengine.tools.util.Logging.initializeLogging(Lo >> gging.java:35) >> at com.google.appengine.tools.development.gwt.AppEngineLauncher >> .start(AppEngineLauncher.java:77) >> at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509) >> at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068) >> at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811) >> at com.google.gwt.dev.DevMode.main(DevMode.java:311) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce >> ssorImpl.java:39) >> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >> thodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at com.intellij.rt.execution.application.AppMain.main(AppMain.j >> ava:120) >> Caused by: java.lang.NullPointerException >> at com.google.appengine.tools.info.SdkInfo.getLibs(SdkInfo.java >> :77) >> at com.google.appengine.tools.info.SdkInfo.determineOptionalLib >> s(SdkInfo.java:284) >> at com.google.appengine.tools.info.SdkInfo.determineOptionalUse >> rLibs(SdkInfo.java:254) >> at com.google.appengine.tools.info.SdkInfo.init(SdkInfo.java:233) >> at com.google.appengine.tools.info.SdkInfo.getSdkRoot(SdkInfo.j >> ava:182) >> at com.google.appengine.tools.info.SdkImplInfo.<clinit>(SdkImpl >> Info.java:19) >> ... 11 more >> >> We keep the sdk in svn since version 1.3.1 and this has never happened >> before. Any ideas on why this is happening? Any solution? >> Thanks. >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/0ZZxdfFmAQAJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
