Google App Engine SDK 1.7.7 is now available!

1,148 views
Skip to first unread message

Richmond Manzana

unread,
Apr 9, 2013, 6:44:38 PM4/9/13
to google-a...@googlegroups.com
Hi everyone,

We're happy to announce that we have released the 1.7.7 SDK.

This release includes new features such as updates to the Maven Plugin, and Outbound Sockets.  We're also happy to announce that we have removed the weekly $2.10 minimum spend for billing enabled apps :)

For more details, please read our blog post and release notes.

Announcement:


Cheers!

Richmond Manzana
Technical Program Manager
Google App Engine

Stefaan Vanderheyden

unread,
Apr 10, 2013, 3:19:04 AM4/10/13
to google-a...@googlegroups.com
Great job! Watch out though, this is the 2nd time that the appengine-maven-plugin is not released to Maven Central at the same time as the rest of your SDK... What's up?

Sekhar

unread,
Apr 10, 2013, 3:15:04 PM4/10/13
to google-a...@googlegroups.com
I'm getting a "appengine-api-1.0-sdk-1.7.7.jar is too large" error when deploying. Are we expected to split this manually or is there a workaround?

Takashi Matsuo

unread,
Apr 10, 2013, 4:33:01 PM4/10/13
to google-a...@googlegroups.com
Hi Stefaan,

Sorry about it, we're going to push it today, and it'll be available hopefully tomorrow.

In the meantime, you can build the snapshot version from the google code repo by:

$ cd appengine-maven-plugin
$ mvn install

Then you'll have the plugin version 1.7.7-SNAPSHOT in your local maven directory, so you can use 1.7.7-SNAPSHOT as the version in your project's pom.xml.
Only one nit is the SNAPSHOT version uses 1.7.6 SDK when uploading, so do as follows:
$ mvn -Dappengine.target.version=1.7.7 appengine:update


--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Takashi Matsuo | Developers Programs Engineer | tma...@google.com

Takashi Matsuo

unread,
Apr 10, 2013, 4:38:51 PM4/10/13
to google-a...@googlegroups.com

Hi Sekhar,

Weird, I don't have such an error. How big is your appengine-api-1.0-sdk-1.7.7.jar?  Which operating system are you using?
Anyway, a possible workaround is to use --enable_jar_splitting option when deploying. Can you try that?


--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Francois Masurel

unread,
Apr 10, 2013, 4:59:40 PM4/10/13
to google-a...@googlegroups.com
Getting also the same "appengine-api-1.0-sdk-1.7.7.jar is too large" error.

I'm on Windows 7 x64 with latest GAE and Java 7 SDK and the appengine-api-1.0-sdk-1.7.7.jar is 30.6MB big.

Thanx for your help.

François

Takashi Matsuo

unread,
Apr 10, 2013, 5:28:42 PM4/10/13
to google-a...@googlegroups.com
Hi Francois,

Thanks for the report. Have you tried it with --enable_jar_splitting?


--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Francois MASUREL

unread,
Apr 10, 2013, 5:35:01 PM4/10/13
to google-a...@googlegroups.com
Yes, without success.


François Masurel


--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/r5JNlfkqq94/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
Message has been deleted

Ludovic Champenois

unread,
Apr 11, 2013, 1:49:11 PM4/11/13
to google-a...@googlegroups.com, mas...@mably.com
Hi,
We are tracking this issue internally...Only on windows, and if your app is using some JSP right?
It's a combination of 2 things: the api jar becoming too big (we will compress it soon), and the jspc compiler keeping a lock on the files in the jspc classpath, making the api jar not deletable (we do not need to upload it to the runtime server)... Windows file locking system makes the locked file non deletable...
Until we push a new SDK, the only workaround would be for you to modify your local SDK this way:
1/ unjar the impacted jar.
2/ rejar it with the jar command default (i.e compression) and making sure you keep all the META-INF manifest (using the m flag) content in the new jar. It contains critical info for the processing.
This will workaround the issue, while waiting for a new push.

Takashi Matsuo

unread,
Apr 11, 2013, 2:45:42 PM4/11/13
to google-a...@googlegroups.com, mas...@mably.com
On Thu, Apr 11, 2013 at 10:49 AM, Ludovic Champenois <lu...@google.com> wrote:
Hi,
We are tracking this issue internally...Only on windows, and if your app is using some JSP right?
It's a combination of 2 things: the api jar becoming too big (we will compress it soon), and the jspc compiler keeping a lock on the files in the jspc classpath, making the api jar not deletable (we do not need to upload it to the runtime server)... Windows file locking system makes the locked file non deletable...
Until we push a new SDK, the only workaround would be for you to modify your local SDK this way:
1/ unjar the impacted jar.
2/ rejar it with the jar command default (i.e compression) and making sure you keep all the META-INF manifest (using the m flag) content in the new jar. It contains critical info for the processing.
This will workaround the issue, while waiting for a new push.

To clarify, we're going to release a minor update for 1.7.7. For the meantime, you can re-jar the file as follows:

cd to the working directory
$ jar xf somewhere\appengine-java-sdk-1.7.7\lib\user\appengine-api-1.0-sdk-1.7.7.jar
$ jar cfm somewhere\appengine-api-1.0-sdk-1.7.7.jar META-INF/MANIFEST.MF *
and replace the old jar with the newly created one.

Sorry for the inconvenience.

tz

unread,
Apr 12, 2013, 12:21:15 PM4/12/13
to google-a...@googlegroups.com
I have the same problem as Panjie:  I can no longer use the api explorer on the local development server, instead it gets redirected to https://developers.google.com/apis-explorer/#p/ 
Message has been deleted

alex

unread,
Apr 12, 2013, 1:22:07 PM4/12/13
to google-a...@googlegroups.com

Vinny P

unread,
Apr 12, 2013, 4:32:07 PM4/12/13
to google-a...@googlegroups.com
Richmond & AppEngine team,

If you're ever in the Chicago area, look me up and I'll buy you a beer. I've been waiting for outbound sockets for years!

A quick issue though: Can you make it explicitly clear in the Sockets API Overview https://developers.google.com/appengine/docs/java/sockets/overview that developers have to include the JavaMail JARs if they need to access IMAP/POP3/SMTP via Javamail? I say this because https://developers.google.com/appengine/docs/java/mail/overview#Sending_Mail_with_the_JavaMail_API states "Do not add Oracle®'s JavaMail JARs to your app." I realize that's an entirely different section, but it makes people believe that AppEngine already packages the full JavaMail library, when truly it doesn't repackage the Provider classes. It would also be fine if you skipped the notice and included the Provider libraries within the AppEngine SDK.

Thanks
-----------------
-Vinny P
Technology & Media Advisor
Chicago, IL

@GOV on AppDotNet: https://alpha.app.net/gov

Rafael

unread,
Apr 12, 2013, 9:50:23 PM4/12/13
to google-appengine
Thanks for this guys. 

We have integrated apple's push system and it seems to work great! 

Eliminating an external server reduces our app development complexity by a lot.

thanks!
rafa


--
Message has been deleted

Jeff Schnitzer

unread,
Apr 15, 2013, 11:25:41 AM4/15/13
to Google App Engine
Can't help you with python, but this bit of Java code works great for me (called via the task queue). It uses this library:


Code:

@Singleton
public class PushService {

/** */
ApnsService service = APNS.newService()
.withCert(this.getClass().getResourceAsStream(CERT), CERT_PW)
.withProductionDestination()
.withNoErrorDetection()
.build();

/**
* @param sound can be null
* @param badge can be null
*/
synchronized public void push(String token, String message, String sound, Integer badge) {
PayloadBuilder bld = APNS.newPayload().alertBody(message);

if (sound != null)
bld = bld.sound(sound);

if (badge != null)
bld = bld.badge(badge);

String payload = bld.build();

service.push(token, payload);
}
}



On Sun, Apr 14, 2013 at 7:58 PM, mike <mik...@gmail.com> wrote:
Do you mind to share a bit on how you integrated APN ?

Did you write the APN code yourself or use existing code?
I need to implement APN in Python as well.

Now I am thinking modify the code here: 

Rafael

unread,
Apr 15, 2013, 4:51:01 PM4/15/13
to google-appengine
Jeff, 

I use the same library, but I had to change their source code, specially the part where it create threads. It should use appengine threadfactory instead. 


I will submit a patch soon, but I'm tight on schedule. 

I have talked too soon about sockets being working nice. Yesterday I have reached max quota on the sockets creation. I don't see why there's a quota at all. It means that I can't send APNS pushes as much as other HTTP integrated api's. 

thanks
rafa

Rafael Sanches

unread,
Apr 15, 2013, 4:50:48 PM4/15/13
to google-appengine
Jeff, 

I use the same library, but I had to change their source code, specially the part where it create threads. It should use appengine threadfactory instead. 


I will submit a patch soon, but I'm tight on schedule. 

I have talked too soon about sockets being working nice. Yesterday I have reached max quota on the sockets creation. I don't see why there's a quota at all. It means that I can't send APNS pushes as much as other HTTP integrated api's. 

thanks
rafa
On Mon, Apr 15, 2013 at 8:25 AM, Jeff Schnitzer <je...@infohazard.org> wrote:

Jeff Schnitzer

unread,
Apr 15, 2013, 4:59:59 PM4/15/13
to Google App Engine
FYI, using withNoErrorDetection() it works on GAE out of the box.

But it would probably be nice to have that feature working.

Jeff
Message has been deleted

ludovic Champenois

unread,
Apr 16, 2013, 11:44:35 PM4/16/13
to google-a...@googlegroups.com
On 4/10/13 2:35 PM, Francois MASUREL wrote:
Yes, without success.


François Masurel

Hi,

The Java App Engine 1.7.7.1 SDK is now available with a fix for this windows specific issue. The Eclipse SDK plugin, as well as the App Engine Maven plugin have also been updated.

Happy coding...
Reply all
Reply to author
Forward
Message has been deleted
0 new messages