[appengine-java] Deployment process with eclipse gae plugin
In my development workflow, I have a staging and a production app ID on GAE. In order to switch between them I have to hand edit the appengine-web.xml and specify the application and the version (or do it in the deploy dialog). This feels like it is rife for errors and is rather a pain in the arse. The reason is because the servlet container reloads as soon as I edit this file and thus my local datastore changes. If I forget to change it back then I'm left wondering what is wrong with my database. What would be nice is if on deployment, the dialog would ask me which version and which application id to deploy to and not actually modify my appengine-web.xml. Just use what I input as parameters for the deployment. I'd love to hear thoughts on how everyone here deals with this. I'd even be open to some command line tools or anything to help manage this. -- 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/-/fvmo25hH8q4J. 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.
Re: [appengine-java] Re: problem with Content-type: null with css files
Just to be clear though, in this case, we *should* have been able to trust the tool (the SDK) to upload the file correctly. I mean there should be some sort of checks and balances for a system like that. In this case, I am deploying to my staging system, seeing the problems with CSS and then being like 'what the f*ck'? If I had had to get a patch out to production quickly, then this would have really screwed things up for me. Getting you guys (Google) to pay attention to this stuff took *weeks* and then another week+ to even get a resolution. I know everyone is working hard and everyone is doing a great job and I really appreciate that, but for people to have good opinions and a trusting sense of GAE, I think that bugs sent to the issue tracker should be at least responded to within 24-48 hours. Even if it is something as simple as we are looking into it. I do that with my own open source projects and I'm just one guy. Google certainly has more resources than I do, so there should be no excuse for letting major bugs sit in the queue for that long. Having to call up Ikai and say hey dude, could you please look into this major deployment issue, just isn't sustainable. thanks for listening. jon On Fri, Jan 13, 2012 at 3:16 PM, Ikai Lan (Google) ika...@google.comwrote: Re: Carter Going a bit off topic, but in general I have always worked at places that stage deployments. That is - you have some environment only accessible by your team that reaches live data after your verification and QA more or less have determined that in the worse case scenario, your change is not destructive in a non-recoverable manner. Alternating versions is a very good way to do this; it also offers you a very easy rollback path. Being able to rollback quickly is absolutely key to working fast when things go sour. If it were me, I'd always alternate versions on deploy and manually switch versions when I have confidence the new version is good, but you've got to find that practice that works best for you. There are bugs that only rear their heads in production. The App Engine team more or less does major version releases by deploying to test clusters, internal clusters, and then, via canarying, to the production cluster. The way staging is usually done for new APIs is that new APIs are usually available in production before we announce the release (they may only be accessible to our whitelisted apps) so we can test that, in production (because production is always a jungle), the new APIs work well. We never do a rollout without first having a rollback plan, which is what you get by alternating versions when you deploy your applications. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Fri, Jan 13, 2012 at 12:40 PM, Carter Maslan car...@maslan.com wrote: Ikai - Our site was unusable for 30 minutes while we quickly downloaded the 1.6.1.1 fix and redeployed with the new SDK. We could have deployed in two phases with a different version so that we could have discovered the bug prior to being live. Is it best practice to alternate between versions with *each and every* deployment in order to catch deployment-specific bugs? Or do you think your deployment-related testing is sufficiently good that we can rely on the integrity of deployment? thanks, Carter On Wed, Jan 11, 2012 at 5:22 PM, Ikai Lan (Google) ika...@google.comwrote: We have an SDK update that resolves this issue on upload (I've also posted in a separate thread about this): http://code.google.com/p/googleappengine/downloads/detail?name=appengine-java-sdk-1.6.1.1.zip -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 10, 2012 at 3:38 PM, Shawn Brown big.coffee.lo...@gmail.com wrote: We think we know what's happening. This is something that is happening at app upload time. Can you try setting a new version name for your app, then passing the --no_batch option when using appcfg.sh? appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] Seems to solve it. I can't reproduce the error as I did by just modifying the spaces in comments in the css file anymore. Shawn -- 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 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. -- 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 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
Re: [appengine-java] Re: problem with Content-type: null with css files
I just ran into it after a push, right after everything reset and with the css mime-type workaround in place. jon On Mon, Jan 9, 2012 at 6:19 PM, Matthew Johnson ijustmakecof...@gmail.comwrote: Ikai, I'm using GAP SDK 1.6.1, and so far, I'm the only dev on my team who's experienced this. Sorry I wasn't clear in my earlier reply to Jon. I did NOT need to use Jon's fix; my mime-mapping entry (seemed to) work fine without the period, but only AFTER I incremented the version number. I pushed twice to the same version number after adding the mime-mapping entry with no results. I just removed the xml entry and deployed to the working version number. The mime-type problem resurfaces without the entry, so I don't think it's a red herring. Here's a point of interest: we use a CSS build process, and the symptom first occurred after a fresh build and a deploy to a new version number. Thinking it was a syntax related error, I pulled the content from the default version of my app and pasted it into the css file in question. This *fixed the problem*. I just confirmed that with my freshly incremented build I can fix the css mime-type issue by copying in css content from the default version, without the mime-mapping entry. Once I use the newer css, the problem resurfaces. Summary: -Mime-mapping entry didn't work until I updated the version number. -After fixing with the new version and Mime-mapping entry, removing the mime-mapping entry reintroduced the problem. -I can also fix the content-type by copying content from my default app's version of the file into this version, and pushing that to the same version (without the mime-mapping entry) Hope these (strange) details help out a bit. Cheers, Matt On Jan 9, 2012, at 5:20 PM, Ikai Lan (Google) wrote: It sounds like the data about this XML snippet is still inconclusive. - Jon Stevens reports that if you change the extension to .css, it works - Matt, in addition to using Jon's fix to the fix, you needed to increment the version to fix the broken mime-type So it's possible the XML snippet might be a red herring and it's something in the deployment/version incrementing mechanism that fixes something about the file being in a bad state. Does anyone else have anything to report? -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Mon, Jan 9, 2012 at 5:01 PM, Matthew Johnson ijustmakecof...@gmail.com wrote: Jon, FYI, this fix didn't work for me until I incremented the version number. Then it worked great. Cheers, Matt On Jan 9, 2012, at 4:39 PM, Jon Stevens wrote: Just did that, redeployed and it didn't fix anything. Edited the part below to have extension.css/extension (adding a period) and now the workaround to the workaround works. jon On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh amyu+gro...@google.com wrote: For those affected, it looks like a workaround is to add the following to your web.xml: mime-mapping extensioncss/extension mime-typetext/css/mime-type /mime-mapping On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens latch...@gmail.com wrote: Well, it seems it isn't just me, so I just filed a ticket: http://code.google.com/p/googleappengine/issues/detail?id=6655 Please star it. jon On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan jcmas...@gmail.com wrote: we had the same problem and it was solved by updating the css file (with a space) and pushing again (without an app version change). Appreciate any info you find on preventing this problem. It behaved as though it was a problem in GAE's caching of static files. On Dec 30, 2011, at 8:34 PM, jnamnath jnamn...@gmail.com wrote: I got it working again by updating the version number in my appengine- web.xml and pushing the new version. Still have no idea what happened here. -J On Dec 24, 4:48 pm, jon stevens latch...@gmail.com wrote: Hey there, I've got an app up on GAE-J that when I request a .css file, I get back a Content-Type: null, which is causing Chrome/Safari to not render the page correctly. Any ideas why this would happen? Here is an example of what I see in the Chrome Developer Tools - Network - Headers. I tried adding the mime-extension to the web.xml and that didn't do anything. Request URL:http://appid.appspot.com/css/gen/main.css Request Method:GET Status Code:200 OK Request Headers Accept:text/css,*/*;q=0.1 Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 Authorization:Basic sldkjf Cache-Control:max-age=0 Connection:keep-alive Host:appid.appspot.com If-None-Match:Cf2J0A Referer:http://appid.appspot.com/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 Response Headers Cache-Control:public, max-age=600 Content-Length:112490 Content
Re: [appengine-java] Re: problem with Content-type: null with css files
Just did that, redeployed and it didn't fix anything. Edited the part below to have extension.css/extension (adding a period) and now the workaround to the workaround works. jon On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh amyu+gro...@google.com wrote: For those affected, it looks like a workaround is to add the following to your web.xml: mime-mapping extensioncss/extension mime-typetext/css/mime-type /mime-mapping On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens latch...@gmail.com wrote: Well, it seems it isn't just me, so I just filed a ticket: http://code.google.com/p/googleappengine/issues/detail?id=6655 Please star it. jon On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan jcmas...@gmail.com wrote: we had the same problem and it was solved by updating the css file (with a space) and pushing again (without an app version change). Appreciate any info you find on preventing this problem. It behaved as though it was a problem in GAE's caching of static files. On Dec 30, 2011, at 8:34 PM, jnamnath jnamn...@gmail.com wrote: I got it working again by updating the version number in my appengine- web.xml and pushing the new version. Still have no idea what happened here. -J On Dec 24, 4:48 pm, jon stevens latch...@gmail.com wrote: Hey there, I've got an app up on GAE-J that when I request a .css file, I get back a Content-Type: null, which is causing Chrome/Safari to not render the page correctly. Any ideas why this would happen? Here is an example of what I see in the Chrome Developer Tools - Network - Headers. I tried adding the mime-extension to the web.xml and that didn't do anything. Request URL:http://appid.appspot.com/css/gen/main.css Request Method:GET Status Code:200 OK Request Headers Accept:text/css,*/*;q=0.1 Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 Authorization:Basic sldkjf Cache-Control:max-age=0 Connection:keep-alive Host:appid.appspot.com If-None-Match:Cf2J0A Referer:http://appid.appspot.com/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 Response Headers Cache-Control:public, max-age=600 Content-Length:112490 Content-Type:null Date:Sun, 25 Dec 2011 00:23:00 GMT ETag:NfQmpA Expires:Sun, 25 Dec 2011 00:33:00 GMT Server:Google Frontend -- 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 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. -- 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 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. -- 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 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. -- 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 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. -- 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 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.
Re: [appengine-java] Re: problem with Content-type: null with css files
I have no idea how your internal systems work, but I'd look into the code which sets the Content-Type header and see what could possibly set it to null or not set it at all and then work back from there. Some more data points for reproduction? My css file is fairly large since I have one file for my entire site: ~143k The file is nested in the war file. /war/css/main.css The file is generated via a bunch of .less files and compiled with lessc. jon On Mon, Jan 9, 2012 at 5:20 PM, Ikai Lan (Google) ika...@google.com wrote: It sounds like the data about this XML snippet is still inconclusive. - Jon Stevens reports that if you change the extension to .css, it works - Matt, in addition to using Jon's fix to the fix, you needed to increment the version to fix the broken mime-type So it's possible the XML snippet might be a red herring and it's something in the deployment/version incrementing mechanism that fixes something about the file being in a bad state. Does anyone else have anything to report? -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Mon, Jan 9, 2012 at 5:01 PM, Matthew Johnson ijustmakecof...@gmail.com wrote: Jon, FYI, this fix didn't work for me until I incremented the version number. Then it worked great. Cheers, Matt On Jan 9, 2012, at 4:39 PM, Jon Stevens wrote: Just did that, redeployed and it didn't fix anything. Edited the part below to have extension.css/extension (adding a period) and now the workaround to the workaround works. jon On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh amyu+gro...@google.com wrote: For those affected, it looks like a workaround is to add the following to your web.xml: mime-mapping extensioncss/extension mime-typetext/css/mime-type /mime-mapping On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens latch...@gmail.com wrote: Well, it seems it isn't just me, so I just filed a ticket: http://code.google.com/p/googleappengine/issues/detail?id=6655 Please star it. jon On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan jcmas...@gmail.com wrote: we had the same problem and it was solved by updating the css file (with a space) and pushing again (without an app version change). Appreciate any info you find on preventing this problem. It behaved as though it was a problem in GAE's caching of static files. On Dec 30, 2011, at 8:34 PM, jnamnath jnamn...@gmail.com wrote: I got it working again by updating the version number in my appengine- web.xml and pushing the new version. Still have no idea what happened here. -J On Dec 24, 4:48 pm, jon stevens latch...@gmail.com wrote: Hey there, I've got an app up on GAE-J that when I request a .css file, I get back a Content-Type: null, which is causing Chrome/Safari to not render the page correctly. Any ideas why this would happen? Here is an example of what I see in the Chrome Developer Tools - Network - Headers. I tried adding the mime-extension to the web.xml and that didn't do anything. Request URL:http://appid.appspot.com/css/gen/main.css Request Method:GET Status Code:200 OK Request Headers Accept:text/css,*/*;q=0.1 Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 Authorization:Basic sldkjf Cache-Control:max-age=0 Connection:keep-alive Host:appid.appspot.com If-None-Match:Cf2J0A Referer:http://appid.appspot.com/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 Response Headers Cache-Control:public, max-age=600 Content-Length:112490 Content-Type:null Date:Sun, 25 Dec 2011 00:23:00 GMT ETag:NfQmpA Expires:Sun, 25 Dec 2011 00:33:00 GMT Server:Google Frontend -- 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 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. -- 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 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. -- 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 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
Re: [appengine-java] Re: problem with Content-type: null with css files
Well, it seems it isn't just me, so I just filed a ticket: http://code.google.com/p/googleappengine/issues/detail?id=6655 Please star it. jon On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan jcmas...@gmail.com wrote: we had the same problem and it was solved by updating the css file (with a space) and pushing again (without an app version change). Appreciate any info you find on preventing this problem. It behaved as though it was a problem in GAE's caching of static files. On Dec 30, 2011, at 8:34 PM, jnamnath jnamn...@gmail.com wrote: I got it working again by updating the version number in my appengine- web.xml and pushing the new version. Still have no idea what happened here. -J On Dec 24, 4:48 pm, jon stevens latch...@gmail.com wrote: Hey there, I've got an app up on GAE-J that when I request a .css file, I get back a Content-Type: null, which is causing Chrome/Safari to not render the page correctly. Any ideas why this would happen? Here is an example of what I see in the Chrome Developer Tools - Network - Headers. I tried adding the mime-extension to the web.xml and that didn't do anything. Request URL:http://appid.appspot.com/css/gen/main.css Request Method:GET Status Code:200 OK Request Headers Accept:text/css,*/*;q=0.1 Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 Authorization:Basic sldkjf Cache-Control:max-age=0 Connection:keep-alive Host:appid.appspot.com If-None-Match:Cf2J0A Referer:http://appid.appspot.com/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 Response Headers Cache-Control:public, max-age=600 Content-Length:112490 Content-Type:null Date:Sun, 25 Dec 2011 00:23:00 GMT ETag:NfQmpA Expires:Sun, 25 Dec 2011 00:33:00 GMT Server:Google Frontend -- 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 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. -- 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 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. -- 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 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.
[appengine-java] problem with Content-type: null with css files
Hey there, I've got an app up on GAE-J that when I request a .css file, I get back a Content-Type: null, which is causing Chrome/Safari to not render the page correctly. Any ideas why this would happen? Here is an example of what I see in the Chrome Developer Tools - Network - Headers. I tried adding the mime-extension to the web.xml and that didn't do anything. Request URL:http://appid.appspot.com/css/gen/main.css Request Method:GET Status Code:200 OK Request Headers Accept:text/css,*/*;q=0.1 Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 Accept-Encoding:gzip,deflate,sdch Accept-Language:en-US,en;q=0.8 Authorization:Basic sldkjf Cache-Control:max-age=0 Connection:keep-alive Host:appid.appspot.com If-None-Match:Cf2J0A Referer:http://appid.appspot.com/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 Response Headers Cache-Control:public, max-age=600 Content-Length:112490 Content-Type:null Date:Sun, 25 Dec 2011 00:23:00 GMT ETag:NfQmpA Expires:Sun, 25 Dec 2011 00:33:00 GMT Server:Google Frontend -- 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/-/7KUDDCJijTkJ. 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.
[appengine-java] Updating Eclipse
Hey googler's... It has been a week now since 1.6.0 has been released. I'd love to see an update to the Eclipse integration to support the new version. Ideally, this would go out on the same day a new version is released. Is there anything I can do to help? thanks, jon -- 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/-/gjYDmsVe-zAJ. 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.
[appengine-java] Re: Updating Eclipse
Yea, that is obvious, but lame. Every time I restart the container, I get this big message saying that an update is available, but I can't actually auto install it. -- 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/-/MGX-v0-3u9oJ. 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.
[appengine-java] Re: Blacklist creation error on boot
I'm seeing this same problem. Doesn't seem to affect anything. My guess is it is leftover crud from a JDK 'upgrade'. jon On Dec 11, 11:47 pm, Yoichi takayama.yoi...@gmail.com wrote: I have the same problem, after Apple's Software Update suggested that a new update for Java 1.6.0 is available and I have told it to update. I have restarted the system just in case, but there is no difference. I am using Eclipse Galileo with GAE SDK and Mac OS X 10.6.1. After the update, when I wanted to test a GAE Web app on the local test server, I get this error message: Dec 12, 2009 7:02:39 AM com.google.appengine.tools.development.agent.impl.BlackList initBlackList SEVERE: Unable to read a jre library while constructing the blacklist. Security restrictions may not be entirely emulated. /System/Library/ Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/plugin.jar $ jar tf /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/ Home/lib/plugin.jar java.io.FileNotFoundException: /System/Library/Frameworks/ JavaVM.framework/Versions/1.6.0/Home/lib/plugin.jar (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at java.io.FileInputStream.init(FileInputStream.java:66) at sun.tools.jar.Main.run(Main.java:206) at sun.tools.jar.Main.main(Main.java:1044) The plugin.jar is there as an alias but the Get INfo does not show that it is not pointing to any original. $ ls -l plugin.jar /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/ plugin.jar - /System/Library/Frameworks/JavaVM.framework/Resources/ Deploy.bundle/Contents/Home/lib/plugin2.jar plugin2.jar does not exist in the destination (Contents of the Deploy.bundle). Instead, we have plugin.jar in the directory. The plugin.jar is an alias and, in turn, pointing to: /System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/ Deploy.bundle/Contents/Resources/Java/plugin.jar I probably can fix the Alias plugin2.jar to plugin.jar and it may all work. What do you suggest in order to fix it? I could use linux command ln, but is that the way? The Apple Finder Show Original does not take me inside the Contents of a bundle. Yoichi -- 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 google-appengine-j...@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.
