[appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
That's on our roadmap, but I'm waiting for Atlassian OnDemand to start supporting maven repos for artifact deployment. It's a good goal, but adding an SDK to subversion shouldn't cause it to break... On Mar 1, 2:34 pm, Jonathan Chen wrote: > On Friday, 2 March 2012 08:24:40 UTC+13, dilbert wrote: > > > 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. > > How about using maven to handle your project dependencies instead? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
On Friday, 2 March 2012 08:24:40 UTC+13, dilbert wrote: > > 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. > How about using maven to handle your project dependencies instead? -- 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/-/r1Udgvt2qC8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
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.(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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
Time to migrate to Git! :-) Jeff On Thu, Mar 1, 2012 at 9:25 AM, 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.ExceptionInInitializ**erError >>at com.google.appengine.tools.uti**l.Logging.initializeLogging(Lo* >> *gging.java:35) >>at com.google.appengine.tools.dev**elopment.gwt.AppEngineLauncher* >> *.start(AppEngineLauncher.java:**77) >>at com.google.gwt.dev.DevMode.doS**tartUpServer(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.mai**n(DevMode.java:311) >>at sun.reflect.NativeMethodAccess**orImpl.invoke0(Native Method) >>at sun.reflect.NativeMethodAccess**orImpl.invoke(NativeMethodAcce* >> *ssorImpl.java:39) >>at sun.reflect.DelegatingMethodAc**cessorImpl.invoke(DelegatingMe* >> *thodAccessorImpl.java:25) >>at java.lang.reflect.Method.invok**e(Method.java:597) >>at com.intellij.rt.execution.appl**ication.AppMain.main(AppMain.j* >> *ava:120) >> Caused by: java.lang.NullPointerException >>at com.google.appengine.tools.inf**o.SdkInfo.getLibs(SdkInfo.java* >> *:77) >>at com.google.appengine.tools.inf**o.SdkInfo.determineOptionalLib* >> *s(SdkInfo.java:284) >>at com.google.appengine.tools.inf**o.SdkInfo.determineOptionalUse* >> *rLibs(SdkInfo.java:254) >>at com.google.appengine.tools.inf**o.SdkInfo.init(SdkInfo.java:23* >> *3) >>at com.google.appengine.tools.inf**o.SdkInfo.getSdkRoot(SdkInfo.j* >> *ava:182) >>at com.google.appengine.tools.inf**o.SdkImplInfo.(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/-/dJrB5UEdA7kJ. > > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
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.(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/-/dJrB5UEdA7kJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
Not sure what you mean by make your .svn directories writable. I develop on linux and all the .svn folders have rwx for the user under which I develop. The development server runs as the same user. Should I make the adjustments for group and others? What about the subfolders inside the .svn folder? Should I mess with them too? This is the exception I get: Exception in thread "main" java.lang.ExceptionInInitializerError at com.google.appengine.tools.util.Logging.initializeLogging(Logging.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(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) Caused by: java.lang.NullPointerException at com.google.appengine.tools.info.SdkInfo.getLibs(SdkInfo.java:77) at com.google.appengine.tools.info.SdkInfo.determineOptionalLibs(SdkInfo.java:284) at com.google.appengine.tools.info.SdkInfo.determineOptionalUserLibs(SdkInfo.java:254) at com.google.appengine.tools.info.SdkInfo.init(SdkInfo.java:233) at com.google.appengine.tools.info.SdkInfo.getSdkRoot(SdkInfo.java:182) at com.google.appengine.tools.info.SdkImplInfo.(SdkImplInfo.java:19) ... 11 more I think this is the relevant issue on the issue tracker: http://code.google.com/p/googleappengine/issues/detail?id=6936 This is still an issue in 1.6.3. Please fix this ASAP. On Thursday, February 23, 2012 3:06:32 AM UTC+1, Max Ross (Google) wrote: > > It's a bug triggered by the fact that the .svn directories are read-only. > If you make those directories writable the problem *should* go away. > Please try that out and let me know. > > Thanks, > Max > -- 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/-/TzYeqGszpiMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
It's a bug triggered by the fact that the .svn directories are read-only. If you make those directories writable the problem *should* go away. Please try that out and let me know. Thanks, Max -- 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/-/KFK8hW26r28J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
And you forgot to mention that if folder is not under svn control everything works perfectly. -- 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/-/3GmbevDQOBQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Problem with exception on server startup when GAE sdk is in svn
I forgot to mention that the same happens with version 1.6.2.1. -- 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/-/aUUxcT7iuQEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
