Re: [google-appengine] Google App Engine Java deployment with gcloud skips almost all files

[Brian de Alwis]

Hi Thomas.

You can deploy your App Engine projects from within Eclipse by selecting the 
project and using the "Deploy to App Engine Standard…" option in the GCP 
toolbar item, or by right-clicking on the project and choosing "Deploy to App 
Engine Standard…".  You can read more at:

https://cloud.google.com/eclipse/docs/deploying

Hope that helps.

Brian.


> On 18-Jun-2018, at 7:07 AM, Thomas Becker  wrote:
> 
> George,
> 
> I'm sure you're right about Maven being the better way to do things. Here's 
> the reason why I haven't gone there. I've been working with the Google App 
> Engine Eclipse plugin since 2010 or so. I recently switched to the new 
> plugin, Google Cloud Tools for Eclipse. After installing that plugin, I was 
> prompted to convert to a Google Cloud Tools project, which I did. Since I 
> wasn't using Maven before, my project was  converted to a non-Maven Google 
> Cloud Tools for Eclipse project. So now what I need to do is convert a 
> non-Maven Google Cloud Tools for Eclipse project to a Maven Google Cloud 
> Tools for Eclipse project. I haven't seen that particular work flow mentioned 
> anywhere in the docs. Any advice, any experience?
> 
> On Sunday, June 17, 2018 at 12:49:45 PM UTC-6, George (Cloud Platform 
> Support) wrote:
> Hello Thomas, 
> 
> This is an excellent observation! Grateful for bringing this apparent 
> discrepancy to our attention. The page you refer to might well have to be 
> brought in tune with the others. Why do I mention the other pages? Because 
> all other Java-related pages and tutorials on cloud.google.com 
> , for instance the collection of tutorials linked 
> to on the "Building an App on App Engine" documentation page 
> , and I 
> stress "all", indicate mvn appengine:deploy as the proper command to deploy a 
> Java app. This cannot be a simple coincidence. 
> 
> Why do you prefer to use gcloud in spite of the general consensus in favor of 
> Maven? Would this meet a special need of yours? Maven offers other 
> advantages, beside ease of app deployment. 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/ad0a2922-dd35-4983-81f7-1d855ad97047%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/021E7D14-ACDA-4694-AAF1-8569AF394055%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Set up Google Cloud SDK or App Engine SDK or both for development?

[Brian de Alwis]

On 17-May-2018, at 9:14 PM, Grass CFA  wrote:
> This is what I have on the Google Cloud Tools settings on Eclipse. If I have 
> unchecked the "Choose SDK" option the SDK Location area was greyed out, so 
> that it stopped me specifying a different SDK location here.

This location is used by Cloud Tools for Eclipse to (1) deploy to GCP and (2) 
to access the development local server (`dev_appserver`) to run and debug App 
Engine Standard apps locally.

> I couldn't find anywhere I can reference the App Engine SDK jars. Are the 
> servlet api and jsp api sufficient for an App Engine project to run? This is 
> really confusing me.

Use the "Google Cloud Libraries" library group.  See the following for details:

https://cloud.google.com/eclipse/docs/libraries

Brian.

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/F97A1B2B-0D11-4949-86A5-CF5B76CD3147%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Set up Google Cloud SDK or App Engine SDK or both for development?

[Brian de Alwis]

Hi.

I find it helpful to think of the Cloud SDK as "programs for manipulating and 
emulating GCP resources".  It doesn't include the APIs and client libraries.

Although the `app-engine-java` component would seem to install the App Engine 
SDK for Java, that installation is an internal implementation detail to the 
Cloud SDK.  It just happens that some of those programs use jars and other 
resources included in the App Engine Java SDK and so it's bundled alongside.

But the Cloud SDK reserves the right to repackage and radically alter the 
`app-engine-java` component.  For example, the Java-based programs could be 
packaged using `jlink` and so the jars would no longer be necessary.

So development tools, such as Cloud Tools for Eclipse, must download and 
install canonical versions of the API jars and dependencies.

Brian.


> On 16-May-2018, at 7:58 PM, Grass CFA  wrote:
> 
> Hello George,
> 
> Thank you for your reply.
> 
> I have instlaled the Google Cloud Tool for Eclipse from Google Marketplace 
> following the instructions. Google Cloud SDK has also been downloaded and 
> installed separately.
> 
> My question was regarding to Google App Engine SDK. It seems the Eclipse 
> automatically uses the SDK jar files from the local Maven repository (see the 
> screenshot as above please) rather than the SDK that I downloaded and 
> installed separately. 
> https://cloud.google.com/appengine/docs/standard/java/download 
> 
> 
> Is it managed by the Google Cloud Tool for Eclipse (gcloud)? How can I 
> configure Eclipse to use the SDK that I downloaded and installed? I couldn't 
> find any instruction as to it.
> 
> Hope it was made clear to you.
> 
> Cheers,
> 
> 
> On Thursday, May 17, 2018 at 3:40:09 AM UTC+10, George (Cloud Platform 
> Support) wrote:
> There are other ways to install the Cloud SDK, the preferred one is in 
> conjunction with installing Cloud Tools for Eclipse. While installing the 
> tools, it searches your computer for the Cloud SDK. If it can't find the SDK, 
> then it automatically downloads the latest version of the SDK. It also 
> periodically checks for and installs updates as needed. Regarding the 
> reference to the SDK from Eclipse, you can either allow Cloud Tools for 
> Eclipse to automatically manage the SDK for you, or you can manage the SDK 
> yourself.
> 
> There is no duplicate work, as the Cloud Tools install searches your computer 
> for the Cloud SDK to reuse it. In short, you can download and install the SDK 
> separately, your work won't get wasted. You may check the "Managing the SDK 
> for Your Project" online document  
> for reference. 
> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/4642397c-a8b6-4d1e-a052-8f8f42d3fe10%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6458AD7B-1B2F-4A71-8A29-774425C82D16%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] OmitStackTraceInFastThrow

[Brian de Alwis]

You might find this conversation helpful:

https://groups.google.com/forum/#!msg/java8-on-gae/ejh4go3DRTA/oqI0Ip9pAQAJ

> On 10-May-2018, at 5:44 AM, Joshua Fox  wrote:
> 
> Does GAE Standard Environment omit stacktraces in fastthrow?
> 
> Using the  JVM  parameter -XX:-OmitStackTraceInFastThrow skips this omission 
> -- i.e., it provides useful stacktrace data. 
> 
> Given that most applications are IO-bound, not CPU-bound, it is good  to have 
>  -XX:-OmitStackTraceInFastThrow 
> 
> How is  Standard Env configured?
>  
> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/CAD%3DB7cM39rOeo59SM-NepF-_wYe5iEbW0sfsr1zO87FQdsGTkg%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5EEC50BD-721F-48CE-8355-47D3651E0D2C%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Multiple apps on Free tier?

[Brian de Alwis]

Hi Jon.

In terms of node.js, you could give Cloud Functions a look: it's node.js priced 
by the request.  It's the same as Firebase Functions.  You can also connect 
Cloud Functions to Firebase Hosting 
Firebase Hosting 
.

And node.js is coming to App Engine.  There's an early access preview that you 
can sign up at:

https://goo.gl/forms/wAYBySsK9sc074hk2

Brian.

> On 2-Mar-2018, at 6:57 PM, Jon Hobbs-Smith  wrote:
> 
> Thanks guys,
> 
> I did try the calculator and unfortunately it seems like the lowest cost I'm 
> going to get away with is around $40/month which to be honest is a lot of 
> money these days to host small personal projects. I can do this on Azure 
> Shared app service for £7/month, and Node is supported on their free tiers.
> 
> Unfortunately this means that a hobbyist trying to learn Node.js isn't going 
> to use Google Cloud :(
> 
> I'm going to try AWS next but if the story is the same I'll go back to Azure.
> 
> 
> 
> On Thursday, 1 March 2018 19:29:57 UTC, Jon Hobbs-Smith wrote:
> Sorry for the newbie question but, well, I am a newbie.
> 
> I am new to GAE (coming from MS Azure) and I can't work out whether it's 
> possible to host multiple website as GAE apps with multiple custom domains 
> without having to page around $30 a month for each one.
> 
> The website mainly small personal sites and programming experiments, my 
> resume etc. so they will use very small amounts of traffic. On MS Azure I 
> would get a single "App service" and run them all on that but I can't work 
> out if that's possible on GAE or, if it is, how usage of the free 28 
> "Instance hours" is calculated?
> 
> Any pointers in the right direction would be really useful as I've spent 
> hours going round in circles with the Google documentation.
> 
> Thanks, Jon.
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/92a66a9d-24e6-4398-8bc7-288c3cb80b35%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8DEB2C11-63B4-4BF5-B1EA-893A3CA4EC95%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Error while deploying spring boot application on standard app engine

[Brian de Alwis]

That bug report (https://github.com/spring-projects/spring-boot/issues/9615) is 
*for* version 1.5.4.  I believe you'll find it fixed in subsequent versions of 
Spring Boot.

See the following project for a working sample app:


https://github.com/GoogleCloudPlatform/getting-started-java/tree/master/appengine-standard-java8/springboot-appengine-standard

It's using 1.5.7.RELEASE.

Brian.

> On 16-Oct-2017, at 9:40 AM, vishakha.saw...@arrk-gcp.co.uk wrote:
> 
> Hi ,
> I am getting below error while deploying sprint boot-AngularJS monolith 
> application on google standard app engine.
> 
> 
> [INFO] GCLOUD: Caused by: 
> [INFO] GCLOUD: org.springframework.aop.framework.AopConfigException: Unable 
> to instantiate proxy using Objenesis, and regular proxy instantiation via 
> default constructor fails as well; nested exception is 
> java.lang.InstantiationException: 
> org.springframework.boot.autoconfigure.web.HttpMessageConverters$$EnhancerBySpringCGLIB$$3ba87c15
> [INFO] GCLOUD: at 
> org.springframework.aop.framework.ObjenesisCglibAopProxy.createProxyClassAndInstance(ObjenesisCglibAopProxy.java:76)
> [INFO] GCLOUD: at 
> org.springframework.aop.framework.CglibAopProxy.getProxy(CglibAopProxy.java:201)
> [INFO] GCLOUD: at 
> org.springframework.aop.framework.ProxyFactory.getProxy(ProxyFactory.java:109)
> [INFO] GCLOUD: at
> 
> I have attached entire stacktrace file with this email. Spring boot version 
> is 1.5.4 and Java version is 8.
> 
> I found old issue raised for this 
> https://github.com/spring-projects/spring-boot/issues/9615. It is closed but 
> It's weird that still I am facing the same issue.
> 
> Do anyone has any idea why we are facing this issue? Let me know if you need 
> more details. 
> 
> Regards,
> 
> Vishakha
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/0cea8630-241b-4db9-92fa-8c988740791c%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/183A8045-0E85-4FAB-A9AF-20CD2E3FF8CF%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Deploying to GAE is down for me, is it down for everyone?

[Brian de Alwis]

GPE had been succeeded by 2 different plugins: the Google-sponsored Cloud Tools 
for Eclipse (CT4E), and the Sencha-backed GWT Plugin for Eclipse. The GWT 
Plugin works with other providers other than App Engine.

There are some migration docs for moving from GPE to CT4E and the GWT Plugin 
(https://cloud.google.com/eclipse/docs/migrating-gpe).

If you're using Datanucleus (long since deprecated with App Engine and 
Datastore), the migration path is harder, unfortunately. One route that is 
reported to work requires converting your project to Maven and use the 
Datanucleus maven plugins. If anybody has had success using the 
Datanucleus-provided Eclipse plugin, please do share!

Brian.

> On Aug 10, 2017, at 5:48 PM, Luis Pinche <luisole...@gmail.com> wrote:
> 
> Will update to eclipse neon and latest google plugin.
> 
> Website says GPE is deprecated, is the GWT plugin the now supported plugin 
> for app engine?
> 
> El jueves, 10 de agosto de 2017, 10:30:54 (UTC-5), Brian de Alwis escribió:
>> 
>> Luis, the suspicion is that you must be running an old version of GPE: when 
>> we try to simulate the issue, GPE discards the stale OAuth data and forces 
>> us to login again.
>> 
>> Could you try updating to the latest version by following the installation 
>> instructions at:
>> 
>>  https://developers.google.com/eclipse/docs/getting_started
>> 
>> Brian.
>> 
>>> On 10-Aug-2017, at 10:30 AM, Brian de Alwis <briand...@gmail.com> wrote:
>>> 
>>> A deprecated OAuth scope (I think was dealing with code.google.com), was 
>>> removed.  But support for this scope was removed years ago from GPE.  I 
>>> suspect that your OAuth refresh token may still carry the scope?  Can you 
>>> try logging out and log back in?
>>> 
>>> Brian.
>>> 
>>>> On 10-Aug-2017, at 12:32 AM, Luis Pinche <luiso...@gmail.com> wrote:
>>>> 
>>>> but how can I change this, this is not code that's part of my app, its the 
>>>> OAUTH window that appears when you let eclipse access your google account 
>>>> to be able to deploy
>>>> 
>>>> 
>>>> El miércoles, 9 de agosto de 2017, 21:43:39 (UTC-5), Kenworth (Google 
>>>> Cloud Platform) escribió:
>>>>> 
>>>>> Make sure you are using the right scope URL. When you run the scope URL 
>>>>> to your browser, it should return a string. 
>>>>> 
>>>>> Example: 
>>>>> 1.1 https://www.googleapis.com/auth/appengine.admin returns 
>>>>> "appengine.admin"
>>>>> 1.2 https://www.googleapis.com/auth/drive returns "drive"
>>>>> 1.3 https://www.googleapis.com/auth/drive.scripts returns "drive.scripts"
>>>>> 
>>>>> For the following, however, it returns an error:
>>>>> 1.4- https://www.googleapis.com/auth/projecthosting
>>>>> 1.5- https://www.googleapis.com/auth/sqlservice 
>>>>> 1.6- https://www.googleapis.com/auth/userinfo#email
>>>>> 
>>>>> You can cross-reference the valid OAuth 2.0 Scopes for Google APIs on 
>>>>> this article. Per this doc, Item #1.6 should be "../userinfo.email" and 
>>>>> not "../userinfo#email".
>>>>> 
>>>>>  
>>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> 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 https://groups.google.com/group/google-appengine.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/google-appengine/abf12d89-45d1-45f3-93c9-32cbdb298250%40googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/ad75a120-5f3b-4180-828b-05b78a4f135e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5FC296C1-B0EC-4C77-8557-D472FF17A41F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Deploying to GAE is down for me, is it down for everyone?

[Brian de Alwis]

Luis, the suspicion is that you must be running an old version of GPE: when we 
try to simulate the issue, GPE discards the stale OAuth data and forces us to 
login again.

Could you try updating to the latest version by following the installation 
instructions at:

https://developers.google.com/eclipse/docs/getting_started

Brian.

> On 10-Aug-2017, at 10:30 AM, Brian de Alwis <briandeal...@gmail.com> wrote:
> 
> A deprecated OAuth scope (I think was dealing with code.google.com 
> <http://code.google.com/>), was removed.  But support for this scope was 
> removed years ago from GPE.  I suspect that your OAuth refresh token may 
> still carry the scope?  Can you try logging out and log back in?
> 
> Brian.
> 
>> On 10-Aug-2017, at 12:32 AM, Luis Pinche <luisole...@gmail.com 
>> <mailto:luisole...@gmail.com>> wrote:
>> 
>> but how can I change this, this is not code that's part of my app, its the 
>> OAUTH window that appears when you let eclipse access your google account to 
>> be able to deploy
>> 
>> 
>> El miércoles, 9 de agosto de 2017, 21:43:39 (UTC-5), Kenworth (Google Cloud 
>> Platform) escribió:
>> Make sure you are using the right scope URL. When you run the scope URL to 
>> your browser, it should return a string. 
>> 
>> Example: 
>> 1.1 https://www.googleapis.com/auth/appengine.admin 
>> <https://www.googleapis.com/auth/appengine.admin> returns "appengine.admin"
>> 1.2 https://www.googleapis.com/auth/drive 
>> <https://www.googleapis.com/auth/drive> returns "drive"
>> 1.3 https://www.googleapis.com/auth/drive.scripts 
>> <https://www.googleapis.com/auth/drive.scripts> returns "drive.scripts"
>> 
>> For the following, however, it returns an error:
>> 1.4- https://www.googleapis.com/auth/projecthosting 
>> <https://www.googleapis.com/auth/projecthosting>
>> 1.5- https://www.googleapis.com/auth/sqlservice 
>> <https://www.googleapis.com/auth/sqlservice> 
>> 1.6- https://www.googleapis.com/auth/userinfo#email 
>> <https://www.googleapis.com/auth/userinfo#email>
>> 
>> You can cross-reference the valid OAuth 2.0 Scopes for Google APIs on this 
>> article <https://developers.google.com/identity/protocols/googlescopes>. Per 
>> this doc, Item #1.6 should be "../userinfo.email" and not 
>> "../userinfo#email".
>> 
>>  
>> 
>> 
>> -- 
>> 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-appengine+unsubscr...@googlegroups.com 
>> <mailto:google-appengine+unsubscr...@googlegroups.com>.
>> To post to this group, send email to google-appengine@googlegroups.com 
>> <mailto:google-appengine@googlegroups.com>.
>> Visit this group at https://groups.google.com/group/google-appengine 
>> <https://groups.google.com/group/google-appengine>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/abf12d89-45d1-45f3-93c9-32cbdb298250%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/abf12d89-45d1-45f3-93c9-32cbdb298250%40googlegroups.com?utm_medium=email_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/C8C49B3F-2D0D-4B18-852D-7E042CB6E426%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Deploying to GAE is down for me, is it down for everyone?

[Brian de Alwis]

A deprecated OAuth scope (I think was dealing with code.google.com), was 
removed.  But support for this scope was removed years ago from GPE.  I suspect 
that your OAuth refresh token may still carry the scope?  Can you try logging 
out and log back in?

Brian.

> On 10-Aug-2017, at 12:32 AM, Luis Pinche  wrote:
> 
> but how can I change this, this is not code that's part of my app, its the 
> OAUTH window that appears when you let eclipse access your google account to 
> be able to deploy
> 
> 
> El miércoles, 9 de agosto de 2017, 21:43:39 (UTC-5), Kenworth (Google Cloud 
> Platform) escribió:
> Make sure you are using the right scope URL. When you run the scope URL to 
> your browser, it should return a string. 
> 
> Example: 
> 1.1 https://www.googleapis.com/auth/appengine.admin 
>  returns "appengine.admin"
> 1.2 https://www.googleapis.com/auth/drive 
>  returns "drive"
> 1.3 https://www.googleapis.com/auth/drive.scripts 
>  returns "drive.scripts"
> 
> For the following, however, it returns an error:
> 1.4- https://www.googleapis.com/auth/projecthosting 
> 
> 1.5- https://www.googleapis.com/auth/sqlservice 
>  
> 1.6- https://www.googleapis.com/auth/userinfo#email 
> 
> 
> You can cross-reference the valid OAuth 2.0 Scopes for Google APIs on this 
> article . Per 
> this doc, Item #1.6 should be "../userinfo.email" and not "../userinfo#email".
> 
>  
> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/abf12d89-45d1-45f3-93c9-32cbdb298250%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/DFDE01C0-E610-4191-B4A4-F164E359EC45%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Plans for Node.js on App Engine Standard?

[Brian de Alwis]

Have you looked at Cloud Functions?  The pricing model is different, but 
there's a free tier too.

https://cloud.google.com/functions/ 

Brian.

> On 19-Jul-2017, at 10:19 PM, Martin Asquino  wrote:
> 
> Hate to necro this thread but.. is this still the case today? And more 
> importantly is there any reason for nodejs not being supported in standard 
> environments? I'm not saying that time or better things to do are not good 
> enough reasons, but I mean like any technical reason for it not to be 
> availabe? Or should I expect this sometime in the future?
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/43baa943-014f-4bd6-9e72-006a2b2fad10%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/51BC5755-B3E1-4C42-B160-ED0DB1933850%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Unable to get TLS 1.2 working on Mac OS

[Brian de Alwis]

I apologize: I misinterpreted what you wrote.  I thought you meant your Python 
interpreter was loading the system ssl.py instead of the version in your 
/usr/local/Cellar.

> On 14-Jun-2017, at 2:36 PM, NP <nearapo...@gmail.com> wrote:
> 
> When you say python path, do you mean?
> 
> >>> python
> >>> import sys
> >>> sys.path
> 
> 
> 
> On Wednesday, June 14, 2017 at 10:41:48 AM UTC-7, Brian de Alwis wrote:
> Do you have a PYTHONPATH, PYTHONSTARTUP, or PYTHONHOME?
> 
> Probably worth trying to launch your python with `-v -v -v` and see where 
> it's loading its files from.
> 
>> On 14-Jun-2017, at 12:52 PM, NP <neara...@gmail.com > wrote:
>> 
>> Can anybody help out here?
>> 
>> Thanks
>> 
>> On Tuesday, June 13, 2017 at 9:30:20 AM UTC-7, NP wrote:
>> 1) I'm running Google App Engine SDK on Mac OS X El Capitan. I have Python 
>> 2.7.13
>> 
>> 
>> 
>> 2) While trying to test my app with Stripe, I get the following error
>> 
>>  Request req_ApPsfecKnLFJxb: Stripe no longer supports API requests made 
>> with TLS 1.0. Please initiate HTTPS connections with TLS 1.2 or later. You 
>> can learn more about thisat https://stripe.com/blog/upgrading-tls 
>> <https://stripe.com/blog/upgrading-tls>.
>> 
>> 
>> 
>> 3) I did some Googling and based on what I found, I did the following
>> 
>> 
>>  Used brew to upgrade my OpenSSL
>> Confirmed that when I do 'which openssl', I get
>> 
>>  /usr/local/opt/openssl/bin/openssl
>> 
>>  and when I do 'openssl version', I get
>> 
>> OpenSSL 1.0.2l
>> 
>> 
>> 
>> 
>> If I do
>> 
>>>>> import ssl
>> 
>>   >>> ssl.OPENSSL_VERSION, I get
>> 
>>   >>> 'OpenSSL 1.0.2l 23 May 2017'
>> 
>> 
>> 
>> But I still get the error from Stripe about not using TLS 1.2.
>> 
>> 
>> 
>> I found this SO question 
>> <https://stackoverflow.com/questions/42566809/enable-tls-1-2-on-mac-osx> but 
>> it didn't solve my problem. I also found this Google Group Discussion 
>> <https://issuetracker.google.com/issues/35900856> and after running the 
>> steps in #5, it shows app engine is still pointing to the old version of 
>> OPENSSL because the output shows 'OpenSSL 0.9.8zh 14 Jan 2016'
>> 
>> 
>> 
>> 4) Based on the earlier referenced Google Group Discussion, I ran the 
>> following code in both GAE Dev and directly in my python intepreter
>> 
>> 
>> 
>> import ssl 
>> 
>> print ssl.__file__ 
>> 
>> 
>> 
>> 
>> 
>> GAE DEV: 
>> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.pyc
>> 
>> 
>> 
>> Python Interpreter: 
>> /usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.pyc
>> 
>> 
>> 
>> 
>> 
>> They're pointing to different files. How do I fix this? How do I get App 
>> Engine to use the newer version of OpenSSL that I've installed?
>> 
>> 
>> -- 
>> 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 https://groups.google.com/group/google-appengine 
>> <https://groups.google.com/group/google-appengine>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/f8b1c84a-5799-479a-b4c0-1867ba10cbb2%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/f8b1c84a-5799-479a-b4c0-1867ba10cbb2%40googlegroups.com?utm_medium=email_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> <mailto:google-appengine+unsubscr...@googlegroups.com>.
> To post to this group, send email to google-appengine@googlegroups.com 
> <mailto:google-appengine@googlegroups.com>.
> Visit this group at https://groups.google.com/group/go

Re: [google-appengine] Re: Unable to get TLS 1.2 working on Mac OS

[Brian de Alwis]

Do you have a PYTHONPATH, PYTHONSTARTUP, or PYTHONHOME?

Probably worth trying to launch your python with `-v -v -v` and see where it's 
loading its files from.

> On 14-Jun-2017, at 12:52 PM, NP  wrote:
> 
> Can anybody help out here?
> 
> Thanks
> 
> On Tuesday, June 13, 2017 at 9:30:20 AM UTC-7, NP wrote:
> 1) I'm running Google App Engine SDK on Mac OS X El Capitan. I have Python 
> 2.7.13
> 
> 
> 
> 2) While trying to test my app with Stripe, I get the following error
> 
>  Request req_ApPsfecKnLFJxb: Stripe no longer supports API requests made 
> with TLS 1.0. Please initiate HTTPS connections with TLS 1.2 or later. You 
> can learn more about thisat https://stripe.com/blog/upgrading-tls 
> .
> 
> 
> 
> 3) I did some Googling and based on what I found, I did the following
> 
> 
>  Used brew to upgrade my OpenSSL
> Confirmed that when I do 'which openssl', I get
> 
>  /usr/local/opt/openssl/bin/openssl
> 
>  and when I do 'openssl version', I get
> 
> OpenSSL 1.0.2l
> 
> 
> 
> 
> If I do
> 
>>>> import ssl
> 
>   >>> ssl.OPENSSL_VERSION, I get
> 
>   >>> 'OpenSSL 1.0.2l 23 May 2017'
> 
> 
> 
> But I still get the error from Stripe about not using TLS 1.2.
> 
> 
> 
> I found this SO question 
>  but 
> it didn't solve my problem. I also found this Google Group Discussion 
>  and after running the steps 
> in #5, it shows app engine is still pointing to the old version of OPENSSL 
> because the output shows 'OpenSSL 0.9.8zh 14 Jan 2016'
> 
> 
> 
> 4) Based on the earlier referenced Google Group Discussion, I ran the 
> following code in both GAE Dev and directly in my python intepreter
> 
> 
> 
> import ssl 
> 
> print ssl.__file__ 
> 
> 
> 
> 
> 
> GAE DEV: 
> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.pyc
> 
> 
> 
> Python Interpreter: 
> /usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.pyc
> 
> 
> 
> 
> 
> They're pointing to different files. How do I fix this? How do I get App 
> Engine to use the newer version of OpenSSL that I've installed?
> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/f8b1c84a-5799-479a-b4c0-1867ba10cbb2%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/37BB0490-968E-4B3B-9AAD-7551356710A6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] NoClassDefFoundError: com/google/appengine/repackaged/com/google/gson/Gson

[Brian de Alwis]

I'd suggest configuring your IDE to ignore any classes found in 
com.google.appengine.repackaged.*. In Eclipse JDT, it's Preferences > Java > 
Appearance > Type Filters.

Brian.

> On 7-Jun-2017, at 4:31 AM, Shachar Grembek  wrote:
> 
> Resolved by changing the import statement to "import com.google.gson.Gson;"
> 
> On Wednesday, June 7, 2017 at 1:52:07 AM UTC+3, Shachar Grembek wrote:
> Hi,
> 
> I had my code run with the new java 8 beta for a few hours, when suddenly 
> some of the code that sed to run perfectly started to raise 500 error of: 
> NoClassDefFoundError: com/google/appengine/repackaged/com/google/gson/Gson
> Can you please advise if there is any possible reason that it stoped working 
> event though I didn't upload any new version
> 
> Thanks
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/6b61d514-53de-4a7c-a9a7-1bed611b2848%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1D3A4E8F-B620-4448-B6D3-0CA93F405D79%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] stuck migrating GAE std in Eclipse from old plugin to Cloud tools for Eclipse

[Brian de Alwis]

That's right: you can remove the jdoconfig.xml.

Brian.

> On 6-Jun-2017, at 6:04 PM, Robert Dyas  wrote:
> 
> Since we don't use JDO at all, can I assume just deleting the jdoconfig.xml 
> file is safe?
> App Engine doesn't need it if JDO isn't used, correct?
> 
> 
> On Monday, June 5, 2017 at 8:36:39 PM UTC-4, Robert Dyas wrote:
> I just upgraded from the Eclipse plugin to Cloud Tools for Eclipse and now my 
> project is a mess.
> 
> I did this: https://cloud.google.com/eclipse/docs/converting 
> 
> 
> I now have a ton of bad imports... for example I have  ton of 
> com.google.appengine.api.datastore references that are now broken.
> 
> What is the best way to get them back? I don't even see a place to download a 
> JAR for it.
> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/a1740a05-d71f-4cf2-9fb8-ed6c2614626c%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/C26DD6B7-A091-4A95-B3F4-D8649618969E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: stuck migrating GAE std in Eclipse from old plugin to Cloud tools for Eclipse

[Brian de Alwis]

Hi Robert.

Just to set expectations, Cloud Tools for Eclipse is a separate product and is 
not considered as the next version of the Google Plugin for Eclipse.  As such, 
CT4E doesn't bring over support for deprecated and superseded products.  You 
can continue to use GPE while you port your code.

The com.google.api.server.spi.SystemServiceServlet is from Cloud Endpoints v1.  
CT4E supports Cloud Endpoints v2.  Cloud Endpoints provides some doc on 
migrating from v1 to v2 
.  
You can use the same approach to adding the Cloud Endpoints v2 jars.

I spent a little bit of time trying to convert a simple JDO+Datastore app to 
use the Datanucleus plugin for Eclipse (http://www.datanucleus.org/downloads/ 
), but hit some issues trying to get a 
workable configuration.  This is what I figured out:
The Datanucleus implementation jars are in the App Engine for Java SDK in 
lib/opt/*/datanucleus/ as v1 or v2.  v1 is for JDO 2, and v2 is for JDO 3.
Copy in /lib/opt/user/datanucleus/v?/*.jar into WEB-INF/lib/
Edit the project properties
Java Build Path: Add WEB-INF/lib/*.jar to your build path
Datanucleus: Add /lib/opt/tools/datanucleus/v?/datanucleus-enhancer-*.jar 
to Datanucleus runtime path
Datanucleus: Uncheck "Use project classpath when running tools" as otherwise 
doesn't pick up the -enhancer.jar
Seems the jdoconfig.xml may need to be placed in WEB-INF/classes/META-INF/.
I hit my time limit and wasn't able to get my sample project to really work.  
But I'm not a JDO/DataNucleus expert, so you might have better success.  To be 
honest, I'd spend my time to convert my project to a Maven project:

https://cloud.google.com/appengine/docs/java/datastore/jdo/overview-dn2 


Brian.

> On 6-Jun-2017, at 12:12 PM, Robert Dyas  wrote:
> 
> And it also doesn't like the src/META-INF/jdoconfig.xml 
> Is this file needed?
> Is there a more correct one to use?
> 
> Description   ResourcePathLocationType
> cvc-elt.1: Cannot find the declaration of element 'jdoconfig'.
> jdoconfig.xml   /ParaSQL/src/META-INF   line 4  XML Problem
> 
> 
> Description   ResourcePathLocationType
> Referenced file contains errors (http://java.sun.com/xml/ns/jdo/jdoconfig).  
> For more information, right click on the message in the Problems View and 
> select "Show Details..."   jdoconfig.xml   /ParaSQL/src/META-INF   line 1 
>  XML Problem
> 
> 
> 
> On Monday, June 5, 2017 at 8:36:39 PM UTC-4, Robert Dyas wrote:
> I just upgraded from the Eclipse plugin to Cloud Tools for Eclipse and now my 
> project is a mess.
> 
> I did this: https://cloud.google.com/eclipse/docs/converting 
> 
> 
> I now have a ton of bad imports... for example I have  ton of 
> com.google.appengine.api.datastore references that are now broken.
> 
> What is the best way to get them back? I don't even see a place to download a 
> JAR for it.
> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/e476abb2-8fae-49fd-908d-801d88878b43%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1D21ADB8-E7B6-4052-A862-020ECD74CAC7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] stuck migrating GAE std in Eclipse from old plugin to Cloud tools for Eclipse

[Brian de Alwis]

Hi Robert.

The new Cloud Tools for Eclipse doesn't automatically add the App Engine jars.  
But it's easily done:

Right click on the project and select Properties…
Switch to the Java Build Path and select the Libraries tab
Click Add Library… and select App Engine Libraries
Select App Engine API

That should resolve com.google .appengine.api.* references.

We'll add this to the conversion doc.  Sorry!

Brian.

> On 5-Jun-2017, at 8:36 PM, Robert Dyas  wrote:
> 
> I just upgraded from the Eclipse plugin to Cloud Tools for Eclipse and now my 
> project is a mess.
> 
> I did this: https://cloud.google.com/eclipse/docs/converting
> 
> I now have a ton of bad imports... for example I have  ton of 
> com.google.appengine.api.datastore references that are now broken.
> 
> What is the best way to get them back? I don't even see a place to download a 
> JAR for it.
> 
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/282643c0-70c8-4d98-b05d-35b130a55ac4%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/BACB754A-5C25-41EE-B372-861E80185633%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Maven plugins

[Brian de Alwis]

On 10-May-2017, at 7:48 AM, Joshua Fox  wrote:
> I guess both approaches provide hot reload? (Debug-time class reloading.)

CT4E uses the same Eclipse facilities used for Java projects to download new 
class definitions to the remote JVM.  This allows in-place modification of a 
class without having to restart the web module, providing the remote JVM allows 
hot-swapping in the changed class definition.

The Maven App Engine plugins support hot reload but with a very different 
approach: it launches the dev_appserver on the exploded war file (i.e., 
extracted on disk) such that the .class files are overwritten during the Maven 
compilation; the dev_appserver detects the file changes and restarts the web 
server.  This usually requires re-connecting to the debugger though.

> What about incremental compilation?  (E..g, add a class or static method and 
> launch the debugger, and only a few relevant class files are recompiled, then 
> launch debug session, with no wait for a war to be  built.)

CT4E is based on Eclipse WTP which supports incremental building and 
publishing.  CT4E doesn't build wars (and the dev_appserver doesn't want a war).

> I should add that we separate our code into multiple Maven-modules for 
> modularity.  (This translates to one Eclipse project per Maven module.) So, 
> the above features would have to work with that.

CT4E leverages m2e-wtp for multi-module support, and it works with no issue 
that we're aware of.

Brian.

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/A1D50FD3-C82F-432F-8581-96FB69C1C8C8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Maven plugins

[Brian de Alwis]

Yup, CT4E connects up the Eclipse Platform/Debug and JDT/Debug support, which 
works across JDWP (a component of JPDA), to debug the dev_appserver.  But 
fortunately nobody needs to ever know about it!

Brian.

> On 9-May-2017, at 2:49 PM, 'Adam (Cloud Platform Support)' via Google App 
> Engine <google-appengine@googlegroups.com> wrote:
> 
> Yes, I should have specified that I meant the project type, not the plugin, 
> since CT4E of course allows you to create a Maven-based project as well. I'm 
> mostly speaking from personal preference. I like the additional options you 
> get with M2Eclipse (like being able to specify a working set), and do most 
> command invocation from a terminal. Hot reload also works fine when debugging 
> this way with 'Build automatically' enabled in Eclipse, as it will replace 
> .class files directly in the target/ directory without needing to invoke a 
> Maven build.
> 
> Thanks Brian for shedding light on how CT4E handles debugging and integration 
> with WTP. My understanding was that the JPDA remote debugger is still used 
> under the hood when debugging locally in WTP, but I am nowhere near an expert 
> on the Eclipse platform. Is this the case?
> 
> On Tuesday, May 9, 2017 at 11:11:00 AM UTC-4, Brian de Alwis wrote:
> CT4E offers two styles of App Engine projects for the standard environment:
> 
> 
> 
> The first one, the Google App Engine Standard Java Project, is a "native" 
> WTP-based Eclipse project style.  The Maven-based Google App Engine Standard 
> Java Project creates a Maven-based project using the new Maven App Engine 
> plugins.  This Maven project uses M2Eclipse and its accompanying m2e-wtp 
> bindings to integrate with Eclipse, which works very well.
> 
> So I believe Adam is recommending using Maven-based projects for important 
> projects, like what is created by the second wizard.  I agree with that 
> recommendation as it allows leveraging the many tools in the Maven ecosystem 
> and works well with existing CI/CD solutions.
> 
> Brian.
> 
>> On 9-May-2017, at 4:59 AM, Joshua Fox  wrote:
>> 
>> 
>> 
>> 
>>  Eclipse incremental compiler and WTP to enable immediate run/debug and 
>> class replacement at debug-time 
>> 
>> Thank  you. That makes sense.
>> 
>> Adam of Cloud Platform Support, your statement (copied immediately below in 
>> blue ) seems to contradict Brian's. Could you please explain?
>>> 
>>> On Sat, May 6, 2017 at 11:08 PM, 'Adam (Cloud Platform Support)' via Google 
>>> App Engine <google-appengine@googlegroups.com 
>>> <mailto:google-appengine@googlegroups.com>> wrote:
>>>  ...
>>> a. Cloud Tools for Eclipse seems to be more of a 'getting started quickly' 
>>> solution, with some UI conveniences but fewer features, so for more serious 
>>> projects I'd personally recommend the Maven plugin.
>>> 
>>> b. This really depends on your needs. There's nothing you can do with the 
>>> Cloud Tools plugin that you can't do with the Maven plugin, and as 
>>> mentioned you can also use both (one is a plugin for Maven via pom.xml, the 
>>> other is for the Eclipse project proper, and they don't mess with each 
>>> other).
>> 
>> 
>> 
>> On Mon, May 8, 2017 at 5:30 PM, Brian de Alwis  wrote:
>> CT4E is to the Maven plugin as m2eclipse is for maven: it uses Eclipse for 
>> what Eclipse does best, and Maven for what Maven does best.  CT4E leverages 
>> the Eclipse incremental compiler and WTP to enable immediate run/debug and 
>> class replacement at debug-time without having to restart the world.  And it 
>> also supports deployment from within Eclipse.
>> 
>> Brian.
>> 
>>> On 8-May-2017, at 9:23 AM, Joshua Fox  wrote:
>>> 
>>>  
>>> On Mon, May 8, 2017 at 4:07 PM, Brian de Alwis  wrote:
>>> Josuha, you can use the Cloud Tools for Eclipse (CT4E, the successor to 
>>> GPE) for launching even with Maven based plugins.
>>> 
>>> Thank you. What added value does CT4E provide as compared to just Maven? 
>>> Note that Adam of Google Support said:
>>>  
>>>  
>>> a. Cloud Tools for Eclipse seems to be more of a 'getting started quickly' 
>>> solution, with some UI conveniences but fewer features, so for more serious 
>>> projects I'd personally recommend the Maven plugin.
>>> b. This really depends on your needs. There's nothing you can do with the 
>>> Cloud Tools plugin that you can't do with the Maven plugin, 
>>> 
>>>  
>>>  
>>> 
>>> I didn't see a reference to this 

Re: [google-appengine] Re: Maven plugins

[Brian de Alwis]

CT4E is to the Maven plugin as m2eclipse is for maven: it uses Eclipse for what 
Eclipse does best, and Maven for what Maven does best.  CT4E leverages the 
Eclipse incremental compiler and WTP to enable immediate run/debug and class 
replacement at debug-time without having to restart the world.  And it also 
supports deployment from within Eclipse.

Brian.

> On 8-May-2017, at 9:23 AM, Joshua Fox <jos...@freightos.com> wrote:
> 
>  
> On Mon, May 8, 2017 at 4:07 PM, Brian de Alwis <briandeal...@gmail.com 
> <mailto:briandeal...@gmail.com>> wrote:
> Josuha, you can use the Cloud Tools for Eclipse (CT4E, the successor to GPE) 
> for launching even with Maven based plugins.
> 
> Thank you. What added value does CT4E provide as compared to just Maven? Note 
> that Adam of Google Support said:
>  
>  
> a. Cloud Tools for Eclipse seems to be more of a 'getting started quickly' 
> solution, with some UI conveniences but fewer features, so for more serious 
> projects I'd personally recommend the Maven plugin.
> b. This really depends on your needs. There's nothing you can do with the 
> Cloud Tools plugin that you can't do with the Maven plugin, 
> 
>  
>  
> 
> I didn't see a reference to this in the email thread, but I'm guessing you're 
> launching multiple services?  Launching multiple services is supported by 
> CT4E.
> 
> 
> No, we are just launching  the builtin dev-appserver that you get when you 
> run Maven goal  appengine:run on the Cloud-SDK Based 
> <https://cloud.google.com/appengine/docs/standard/java/tools/using-maven> 
> Maven plugin. Of course, I don't insist on using Maven to launch. Whatever it 
> takes to avoid launching two processes just to debug ( appengine:run  plus 
> the "remote" debugger).
> 
> 
> With regard to Flex, CT4E is concentrating on the deployment side of the 
> story.
> 
> Right. Deployment in an Eclipse tool is less valuable to us, as we have 
> Jenkins setup to deploy. In fact, Google Support, in early 2017, told us that 
> CT4E does not support  Flex Env. I think they were referring to limitations 
> in deployment and a local Dockerized Flex -- but we do not need those.
>  
>  For run/debug, the solutions right now are to use the Maven goals or other 
> plugins like Run Jetty Run:
> 
>   https://marketplace.eclipse.org/content/run-jetty-run 
> <https://marketplace.eclipse.org/content/run-jetty-run>
> 
> Debugging of a Flex-like (not supporting GAE APIs) local environment inside  
> Eclipse is possible with the Jetty Maven plugin. 
> <https://cloud.google.com/appengine/docs/flexible/java/dev-jetty9>  
> 
> But  I guess you are saying that  Run  Jetty Run 
> <https://marketplace.eclipse.org/content/run-jetty-run> would make this more 
> efficient? I.e., we'd have one debug process rather than '"remote" debugging; 
> and we'd avoid build time in which Maven constructs wars? If that can be done 
>  for a Standard-Env-like local dev environment  (of the sort supported by the 
>  Cloud-SDK Based 
> <https://cloud.google.com/appengine/docs/standard/java/tools/using-maven> 
> Maven plugin or the old Google Plugin for Eclipse), that would be excellent!
> 
> Brian.
> 
>> On 8-May-2017, at 6:43 AM, Joshua Fox <jos...@freightos.com 
>> <mailto:jos...@freightos.com>> wrote:
>> 
>> We have been using the  Google Plugin for Eclipse (now end-of-life). There, 
>> we are  able to launch an Eclipse Debug configuration that puts us right 
>> into the debugger.  (Screenshot attached.)
>> 
>> Launching two separate processes (first appengine:runfrom the 
>> Cloud-SDK-Based 
>> <https://cloud.google.com/appengine/docs/standard/java/tools/using-maven> 
>> Maven plugin, then the remote debug process) is particularly inconvenient 
>> given that dozens of developer must  do this many  times a day.
>> 
>> We'd like to have the same simplicity of a single launch.
>> 
>> 
>> 
>> On Sun, May 7, 2017 at 9:38 PM, 'Adam (Cloud Platform Support)' via Google 
>> App Engine <google-appengine@googlegroups.com 
>> <mailto:google-appengine@googlegroups.com>> wrote:
>> I'm not sure I follow. You need to launch the dev_appserver process anyway 
>> to run your application locally. You're just passing extra JVM flags to 
>> enable the remote debugger so JDB can talk to it. AFAIK you need to enable 
>> the JPDA remote debugger to debug any Jetty app (or servlet container app 
>> for that matter). It's not a limitation of App Engine or the plugins.
>> 
>> On Sunday, May 7, 2017 at 9:01:22 AM UTC-4, Joshua Fox wrote:
>> 
>> 
>> On Sat, May

Re: [google-appengine] Re: Maven plugins

[Brian de Alwis]

Josuha, you can use the Cloud Tools for Eclipse (CT4E, the successor to GPE) 
for launching even with Maven based plugins.

> Launching two separate processes (first appengine:runfrom the Cloud-SDK-Based 
>  
> Maven plugin, then the remote debug process) is particularly inconvenient 
> given that dozens of developer must  do this many  times a day.


I didn't see a reference to this in the email thread, but I'm guessing you're 
launching multiple services?  Launching multiple services is supported by CT4E.

With regard to Flex, CT4E is concentrating on the deployment side of the story. 
 For run/debug, the solutions right now are to use the Maven goals or other 
plugins like Run Jetty Run:

https://marketplace.eclipse.org/content/run-jetty-run

Brian.

> On 8-May-2017, at 6:43 AM, Joshua Fox  wrote:
> 
> We have been using the  Google Plugin for Eclipse (now end-of-life). There, 
> we are  able to launch an Eclipse Debug configuration that puts us right into 
> the debugger.  (Screenshot attached.)
> 
> Launching two separate processes (first appengine:runfrom the Cloud-SDK-Based 
>  
> Maven plugin, then the remote debug process) is particularly inconvenient 
> given that dozens of developer must  do this many  times a day.
> 
> We'd like to have the same simplicity of a single launch.
> 
> 
> 
> On Sun, May 7, 2017 at 9:38 PM, 'Adam (Cloud Platform Support)' via Google 
> App Engine  > wrote:
> I'm not sure I follow. You need to launch the dev_appserver process anyway to 
> run your application locally. You're just passing extra JVM flags to enable 
> the remote debugger so JDB can talk to it. AFAIK you need to enable the JPDA 
> remote debugger to debug any Jetty app (or servlet container app for that 
> matter). It's not a limitation of App Engine or the plugins.
> 
> On Sunday, May 7, 2017 at 9:01:22 AM UTC-4, Joshua Fox wrote:
> 
> 
> On Sat, May 6, 2017 at 11:08 PM, 'Adam (Cloud Platform Support)' via Google 
> App Engine  > wrote:
> 1. If I want to debug my projects without using "remote debugging"? 
> You need to use remote debugging to debug App Engine applications in Eclipse 
> as the debugger must connect to the Jetty instance running on localhost.
> 
> This is inconvenient.  Every time a developer runs their code, they have to 
> launch two processes. Is there a plan to improve that?
> 
> 
> 
> a. You don't need to use Google Cloud Tools for Eclipse as both maven plugins 
> support the jvmFlags option which allows you to provide the necessary JVM 
> flags for debugging 
> :
> 
> 
> 
>   -Xdebug
>   
> -Xrunjdwp:transport=dt_socket,address=,server=y,suspend=n
> 
>   
>   
> See the related discussion in an issue 
> 
>  on the old plugin's project page for a solution involving Maven profiles 
> (this applies equally to the new plugin as the same parameter is supported).
> 
> b. The ability to connect the debugger isn't dependent on the version of 
> dev_appserver, which is mostly a Python wrapper around Jetty, so yes you 
> would still be able to debug with either plugin. Note that as Jeff mentioned 
> you can also use both plugins in your project.
> 
> 2. What is the recommended development setup for Standard Env?
> a. Cloud Tools for Eclipse seems to be more of a 'getting started quickly' 
> solution, with some UI conveniences but fewer features, so for more serious 
> projects I'd personally recommend the Maven plugin.
> 
> b. This really depends on your needs. There's nothing you can do with the 
> Cloud Tools plugin that you can't do with the Maven plugin, and as mentioned 
> you can also use both (one is a plugin for Maven via pom.xml, the other is 
> for the Eclipse project proper, and they don't mess with each other).
> 
> 3. What is the recommended development setup  for Flex Env development?
> No special App-Enginey bits are needed to test a flexible runtime app locally 
> or manage it in Eclipse. This is covered in the docs 
> ;
>  you can use mvn jetty:run-exploded with the Jetty plugin if you're on a 
> Jetty based runtime or just mvn package; java -jar target/myjar.jar on any 
> other runtime. A flexible runtime Java app is essentially just a Dockerized 
> Java app that happens to run on the Flexible runtime.
> 
> On Wednesday, May 3, 2017 at 8:03:33 AM UTC-4, Joshua Fox wrote:
> A question about Google Cloud Tools for Eclipse  
> 

Re: [google-appengine] Re: Cron tasks not uploaded using Google Cloud Tools for Eclipse

[Brian de Alwis]

Jason, 

This will be fixed in the next release of Cloud Tools for Eclipse.

In the meantime you should be able to use the `appcfg.sh` command [1] to upload 
your cron.xml (`appcfg.sh help update_cron`) and `queue.xml` (`appcfg.sh help 
update_queues`).  You'll need to use the `-A` argument to specify your Project 
ID if you don't have an `` element in your appengine-web.xml.

Brian.

[1] appcfg.sh is from the App Engine SDK for Java 
  and not 
included in the Google Cloud SDK.  But it's a simple wrapper around a jar that 
is included in the Google Cloud SDK:

$ java -cp 
$GOOGLE_CLOUD_SDK_HOME/platform/google_appengine/google/appengine/tools/java/lib/appengine-tools-api.jar
 com.google.appengine.tools.admin.AppCfg [args]


> On 31-Mar-2017, at 9:18 PM, Jason  wrote:
> 
> What if you are not using a Maven-based project? I created a non-maven 
> project and it is not uploading my queue.xml or cron.xml either.
> 
> On Wednesday, March 15, 2017 at 3:23:46 AM UTC-7, Nicola Spreafico wrote:
> If you're using a Maven-based project, by default implementation of the Maven 
> Plugin only the app.yaml file (the application itself) is deployed.
> 
> If you need to deploy the cron, queue and index as well, you need to 
> configure the deployables configuration with all the files
> Please see this issue 
>  where I 
> posted a configuration example.
> 
> With the default configuration of the Maven plugin, your configuration will 
> be something like this:
> 
>  target/appengine-staging/app.yaml
>  target/appengine-staging/cron.yaml
>  target/appengine-staging/queue.yaml
>  target/appengine-staging/index.yaml
> 
> 
> Il giorno martedì 14 marzo 2017 22:35:19 UTC+1, Daniel Garrido ha scritto:
> Hi all,
> 
> I have tried to create a cron task using cron.xml file:
> 
> 
> 
>   
> /save
> daily summary job
> every 2 minutes
>   
> 
> 
> When I deploy my app to app engine using Google Cloud Tools for Eclipse, the 
> cron task is not being created (it doesn't appear in the console).
> 
> I tested the same example using the old Eclipse plugin and it worked.
> 
> It seems that the cron.xml file is not being uploaded. Documentation 
> (https://cloud.google.com/appengine/docs/standard/java/config/cron 
> ) says 
> that I have to upload cron tasks using appcfg. This is automatically 
> performed by the eclipse plugin.
> 
> Finally, I used appcfg and the cron task was created.
> 
> I am wondering if I can do the same using the new Google Cloud Tools in an 
> automatic way.
> 
> Best regards,
> Daniel.
> 
> -- 
> 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-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/735dac15-28f2-4b86-893f-6c9f103768d1%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/50C97C9D-CC66-4274-8A59-AD3C048979C7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Help troubleshooting running under the development server

[Brian de Alwis]

In my experience, "bad runtime process port" usually indicates that something 
is writing to System.out.  It seems the dev_appserver communicates to the 
spawned JVMs via stdin/stdout, and so any other messages interfere.

Brian.

> On 26-Feb-2017, at 6:32 PM, 'Adam (Cloud Platform Support)' via Google App 
> Engine  wrote:
> 
> We've seen this error occasionally but reproducing it has been hit or miss. 
> I'd advise filing an issue on the googleappengine issue tracker  
> and uploading a sample 
> app which exhibits the problem. If you provide a link to the issue I will 
> pick it up from there.
> 
> On Saturday, February 25, 2017 at 12:07:47 PM UTC-5, Kevin Wise wrote:
> I have an exceptionally strange situation. My web app, running on Guice in a 
> app engine standard environment, works fine in a development environment on 
> Linux or Mac, but doesn't work on Windows. The symptom is that when I try to 
> run the application, it appears to startup, but then always responds with a 
> 500 error. The log reports:
> 
> ERROR2017-02-24 15:06:29,865 http_proxy.py:116] bad runtime process port 
> ['']
> INFO 2017-02-24 15:06:29,964 module.py:806] default: "GET / HTTP/1.1" 500 
> 4379
> 
> Even stranger, the server returns the log file contents to the browser.  Here 
> is a sample of the browser output:
> 
> bad runtime process port ['']
> 
> Feb 24, 2017 3:04:52 PM 
> com.google.appengine.tools.development.AbstractContainerService configure
> WARNING: Null value for 
> containerConfigProperties.get(devappserver.portMappingProvider)
> Feb 24, 2017 3:04:52 PM com.google.apphosting.utils.jetty.JettyLogger info
> INFO: Logging to JettyLogger(null) via 
> com.google.apphosting.utils.jetty.JettyLogger
> Feb 24, 2017 10:04:52 PM com.google.apphosting.utils.jetty.JettyLogger info
> INFO: jetty-6.1.x
> Feb 24, 2017 10:05:15 PM org.hibernate.validator.internal.util.Version 
> 
> INFO: HV01: Hibernate Validator 5.2.4.Final
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider as a 
> provider class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.sample.health.HealthCheckResource as a root resource 
> class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.example.appengine.helloworld.HelloResource as a root 
> resource class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.sample.exception.ConflictExceptionMapper as a provider 
> class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.sample.exception.IllegalArgumentExceptionMapper as a 
> provider class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory register
> INFO: Registering com.sample.webjars.JaxRsWebjarsServlet as a root resource 
> class
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
> INFO: Initiating Jersey application, version 'Jersey: 1.19.3 10/24/2016 03:43 
> PM'
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.sample.exception.ConflictExceptionMapper to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.sample.exception.IllegalArgumentExceptionMapper to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.sample.health.HealthCheckResource to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.example.appengine.helloworld.HelloResource to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM 
> com.sun.jersey.guice.spi.container.GuiceComponentProviderFactory 
> getComponentProvider
> INFO: Binding com.sample.webjars.JaxRsWebjarsServlet to 
> GuiceManagedComponentProvider with the scope "Singleton"
> Feb 24, 2017 10:05:19 PM com.google.apphosting.utils.jetty.JettyLogger info
> INFO: Started SelectChannelConnector@localhost:54117
>