[google-appengine] Re: Test and Upgrade your App Engine Java Application to a Java 7 runtime...now.

[Ludovic Champenois]

Hi,
A quick status on the Java 7 migration: No news is good news right?
Applications (very large and small)  having tried or even completely 
upgraded to the Java 7 runtime have not discovered runtime issue: this is 
great news!
More applications every single day, and counting...

If you have not started testing your application with the new Java 7 
runtime, this is the right time now to do it either with the current 1.7.5 
release, or the coming 1.7.6 release (we push a preview SDK earlier this 
week).

Cheers.

On Wednesday, February 27, 2013 10:37:01 AM UTC-8, Ludovic Champenois wrote:
>
> Hi,
>
> As part of Google App Engine 1.7.5 release on February 13, 2013, we 
> introduced Preview support of App Engine Java 7 runtime.  In early April, 
> Google will commence upgrading our internal applications from Java 6 to 
> Java 7.  In conjunction with this effort, we highly recommend that all of 
> our App Engine customers begin testing and eventually migrate their 
> applications to Java 7 runtime within the next couple of months. 
>
> Please find below some additional technical information to assist with 
> testing and migrating your application to Java 7 environment:
>
> *Java 6 and Java 7 Compatibility*
>  
> In general, Java 7 runtime is backwards compatible with Java 6, and will 
> run all pre-existing Java applications that did not rely on 
> implementation-specific functionality.  Please refer to the Oracle white 
> paper on Java 7 and Java 
> 6compatibility
>  for additional details.
>
> *Procedure for Testing*
>  
> For all your Java App Engine applications, here are the steps for testing 
> in the new Java 7 environment.
>
> 1.  App Engine can support multiple live versions of a given application. 
>  It is best to create a new version of your app and deploy it to a Java 7 
> runtime.
>
> 2.  You can deploy to a new Java 7 runtime with one of the following steps:
>
> a)  Recompile your Java Application with a full JDK 7 compiler. You can 
> test it with the GAE 1.7.5 SDK, and when ready, use the regular appcfg SDK 
> tool that will detect that the Java byte code is Java 7 compliant and will 
> use a Java7 runtime for this application version.
>
> b)  If you are still compiling your Java application with a JDK 6 
> compiler, you can deploy to the Java 7 runtime by adding the 
> *--use_java7*flag to the appcfg SDK tool.
>
> Please review the Google Java 7 
> Considerationspaper 
> for additional information on configuring Java 7. 
>
> 3.  Assuming you have your default application version still running with 
> a Java 6 runtime and a new version running in Java 7, you can use the 
> Google App Engine Traffic Splitting feature to slowly ramp up traffic on 
> the new Java 7 runtime.  Consider starting with 5%, then increase gradually 
> to 10%, 20%, and so on as your app is behaving as expected.  See our Traffic 
> Splitting 
> documentfor
>  more information about this tool.
>
> Thanks for spending the time to make sure your application is Java 7 ready 
> now. Only a very few incompatible behaviors may have to be fixed in your 
> applications. 
>
>  
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Test and Upgrade your App Engine Java Application to a Java 7 runtime...now.

[Ludovic Champenois]

Hi,

It's coming! Are you ready?

Google App Engine Java SDK 1.7.7 (shipping very soon) will deploy all Java 
applications to the new Java 7 runtime. Did you do a sanity test with your 
current Java applications?  Many of you have done it already: Thank you! So 
far, no migration issues have been reported.

In general, Java 7 runtime is backwards compatible with Java 6, and will 
run all pre-existing Java applications that did not rely on 
implementation-specific functionality.  Please refer to the Oracle white 
paper on Java 7 and Java 
6 
compatibility 
for additional details.

It is still time to try deploying a new version of your application with 
the --use_java7 flag with the appcfg tool and and see that your application 
is behaving as before. Remenber that this flag will be on by default going 
forward in GAE 1.7.7. In the near future all App Engine Java applications 
will run a the new Java 7 runtime.

Cheers.


On Thursday, March 14, 2013 6:56:32 PM UTC-7, Ludovic Champenois wrote:
>
> Hi,
> A quick status on the Java 7 migration: No news is good news right?
> Applications (very large and small)  having tried or even completely 
> upgraded to the Java 7 runtime have not discovered runtime issue: this is 
> great news!
> More applications every single day, and counting...
>
> If you have not started testing your application with the new Java 7 
> runtime, this is the right time now to do it either with the current 1.7.5 
> release, or the coming 1.7.6 release (we push a preview SDK earlier this 
> week).
>
> Cheers.
>
> On Wednesday, February 27, 2013 10:37:01 AM UTC-8, Ludovic Champenois 
> wrote:
>>
>> Hi,
>>
>> As part of Google App Engine 1.7.5 release on February 13, 2013, we 
>> introduced Preview support of App Engine Java 7 runtime.  In early April, 
>> Google will commence upgrading our internal applications from Java 6 to 
>> Java 7.  In conjunction with this effort, we highly recommend that all of 
>> our App Engine customers begin testing and eventually migrate their 
>> applications to Java 7 runtime within the next couple of months. 
>>
>> Please find below some additional technical information to assist with 
>> testing and migrating your application to Java 7 environment:
>>
>> *Java 6 and Java 7 Compatibility*
>>  
>> In general, Java 7 runtime is backwards compatible with Java 6, and will 
>> run all pre-existing Java applications that did not rely on 
>> implementation-specific functionality.  Please refer to the Oracle white 
>> paper on Java 7 and Java 
>> 6compatibility
>>  for additional details.
>>
>> *Procedure for Testing*
>>  
>> For all your Java App Engine applications, here are the steps for testing 
>> in the new Java 7 environment.
>>
>> 1.  App Engine can support multiple live versions of a given application. 
>>  It is best to create a new version of your app and deploy it to a Java 7 
>> runtime.
>>
>> 2.  You can deploy to a new Java 7 runtime with one of the following 
>> steps:
>>
>> a)  Recompile your Java Application with a full JDK 7 compiler. You can 
>> test it with the GAE 1.7.5 SDK, and when ready, use the regular appcfg SDK 
>> tool that will detect that the Java byte code is Java 7 compliant and will 
>> use a Java7 runtime for this application version.
>>
>> b)  If you are still compiling your Java application with a JDK 6 
>> compiler, you can deploy to the Java 7 runtime by adding the *--use_java7
>> * flag to the appcfg SDK tool.
>>
>> Please review the Google Java 7 
>> Considerationspaper 
>> for additional information on configuring Java 7. 
>>
>> 3.  Assuming you have your default application version still running with 
>> a Java 6 runtime and a new version running in Java 7, you can use the 
>> Google App Engine Traffic Splitting feature to slowly ramp up traffic on 
>> the new Java 7 runtime.  Consider starting with 5%, then increase gradually 
>> to 10%, 20%, and so on as your app is behaving as expected.  See our Traffic 
>> Splitting 
>> documentfor
>>  more information about this tool.
>>
>> Thanks for spending the time to make sure your application is Java 7 
>> ready now. Only a very few incompatible behaviors may have to be fixed in 
>> your applications. 
>>
>>  
>>
>

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Re: Test and Upgrade your App Engine Java Application to a Java 7 runtime...now.

[Takashi Matsuo]

Hi,

FWIW, our official maven plugin also supports Java 7. Please use the
following configurations:


org.apache.maven.plugins
2.5.1
maven-compiler-plugin
**
*1.7*
*1.7*
**


com.google.appengine
appengine-maven-plugin
${appengine.target.version}
**
*true*
**



On Thu, Mar 14, 2013 at 6:56 PM, Ludovic Champenois  wrote:

> Hi,
> A quick status on the Java 7 migration: No news is good news right?
> Applications (very large and small)  having tried or even completely
> upgraded to the Java 7 runtime have not discovered runtime issue: this is
> great news!
> More applications every single day, and counting...
>
> If you have not started testing your application with the new Java 7
> runtime, this is the right time now to do it either with the current 1.7.5
> release, or the coming 1.7.6 release (we push a preview SDK earlier this
> week).
>
> Cheers.
>
> On Wednesday, February 27, 2013 10:37:01 AM UTC-8, Ludovic Champenois
> wrote:
>>
>> Hi,
>>
>> As part of Google App Engine 1.7.5 release on February 13, 2013, we
>> introduced Preview support of App Engine Java 7 runtime.  In early April,
>> Google will commence upgrading our internal applications from Java 6 to
>> Java 7.  In conjunction with this effort, we highly recommend that all of
>> our App Engine customers begin testing and eventually migrate their
>> applications to Java 7 runtime within the next couple of months.
>>
>> Please find below some additional technical information to assist with
>> testing and migrating your application to Java 7 environment:
>>
>> *Java 6 and Java 7 Compatibility*
>>
>> In general, Java 7 runtime is backwards compatible with Java 6, and will
>> run all pre-existing Java applications that did not rely on
>> implementation-specific functionality.  Please refer to the Oracle white
>> paper on Java 7 and Java 
>> 6compatibility
>>  for additional details.
>>
>> *Procedure for Testing*
>>
>> For all your Java App Engine applications, here are the steps for testing
>> in the new Java 7 environment.
>>
>> 1.  App Engine can support multiple live versions of a given application.
>>  It is best to create a new version of your app and deploy it to a Java 7
>> runtime.
>>
>> 2.  You can deploy to a new Java 7 runtime with one of the following
>> steps:
>>
>> a)  Recompile your Java Application with a full JDK 7 compiler. You can
>> test it with the GAE 1.7.5 SDK, and when ready, use the regular appcfg SDK
>> tool that will detect that the Java byte code is Java 7 compliant and will
>> use a Java7 runtime for this application version.
>>
>> b)  If you are still compiling your Java application with a JDK 6
>> compiler, you can deploy to the Java 7 runtime by adding the *--use_java7
>> * flag to the appcfg SDK tool.
>>
>> Please review the Google Java 7 
>> Considerationspaper 
>> for additional information on configuring Java 7.
>>
>> 3.  Assuming you have your default application version still running with
>> a Java 6 runtime and a new version running in Java 7, you can use the
>> Google App Engine Traffic Splitting feature to slowly ramp up traffic on
>> the new Java 7 runtime.  Consider starting with 5%, then increase gradually
>> to 10%, 20%, and so on as your app is behaving as expected.  See our Traffic
>> Splitting 
>> documentfor
>>  more information about this tool.
>>
>> Thanks for spending the time to make sure your application is Java 7
>> ready now. Only a very few incompatible behaviors may have to be fixed in
>> your applications.
>>
>>
>>
>  --
> 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 http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Takashi Matsuo | Developers Advocate | tmat...@google.com

-- 
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 http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [google-appengine] Re: Test and Upgrade your App Engine Java Application to a Java 7 runtime...now.

[Thomas Becker]

I actually did find two issues. When migrating to Java 7, one needs to 
upgrade  from JDO 2.3 (datanucleus plugin v1) to JDO 3.0 (datanucleus 
plugin v2). This is stated in the documentation at the very end of the page 

https://developers.google.com/appengine/docs/java/java7 . 

But JDO 3.0 (datanucleus plugin v2) has two serious issues: count queries 
don't work anymore, and the annotation @Persistent(serialized = "true") 
does not work anymore. I submitted these on February 28 as issues #8902 and 
#8903 in the GAE issue tracker. They are both still unaddressed. Before 
switching to Java 7 and deprecating Java 6, please make sure that JDO 3.0 
(datanucleus plugin v2) is fully functional and tested. Otherwise, you will 
breaking apps that use these two features of JDO.


On Friday, March 15, 2013 1:33:43 AM UTC-7, Takashi Matsuo (Google) wrote:
>
>
> Hi,
>
> FWIW, our official maven plugin also supports Java 7. Please use the 
> following configurations:
>
> 
> org.apache.maven.plugins
> 2.5.1
> maven-compiler-plugin
> **
> *1.7*
> *1.7*
> **
> 
> 
> com.google.appengine
> appengine-maven-plugin
> ${appengine.target.version}
> **
> *true*
> **
> 
>
>
> On Thu, Mar 14, 2013 at 6:56 PM, Ludovic Champenois 
> 
> > wrote:
>
>> Hi,
>> A quick status on the Java 7 migration: No news is good news right?
>> Applications (very large and small)  having tried or even completely 
>> upgraded to the Java 7 runtime have not discovered runtime issue: this is 
>> great news!
>> More applications every single day, and counting...
>>
>> If you have not started testing your application with the new Java 7 
>> runtime, this is the right time now to do it either with the current 1.7.5 
>> release, or the coming 1.7.6 release (we push a preview SDK earlier this 
>> week).
>>
>> Cheers.
>>
>> On Wednesday, February 27, 2013 10:37:01 AM UTC-8, Ludovic Champenois 
>> wrote:
>>>
>>> Hi,
>>>
>>> As part of Google App Engine 1.7.5 release on February 13, 2013, we 
>>> introduced Preview support of App Engine Java 7 runtime.  In early April, 
>>> Google will commence upgrading our internal applications from Java 6 to 
>>> Java 7.  In conjunction with this effort, we highly recommend that all of 
>>> our App Engine customers begin testing and eventually migrate their 
>>> applications to Java 7 runtime within the next couple of months. 
>>>
>>> Please find below some additional technical information to assist with 
>>> testing and migrating your application to Java 7 environment:
>>>
>>> *Java 6 and Java 7 Compatibility*
>>>  
>>> In general, Java 7 runtime is backwards compatible with Java 6, and will 
>>> run all pre-existing Java applications that did not rely on 
>>> implementation-specific functionality.  Please refer to the Oracle 
>>> white paper on Java 7 and Java 
>>> 6compatibility
>>>  for additional details.
>>>
>>> *Procedure for Testing*
>>>  
>>> For all your Java App Engine applications, here are the steps for 
>>> testing in the new Java 7 environment.
>>>
>>> 1.  App Engine can support multiple live versions of a given 
>>> application.  It is best to create a new version of your app and deploy it 
>>> to a Java 7 runtime.
>>>
>>> 2.  You can deploy to a new Java 7 runtime with one of the following 
>>> steps:
>>>
>>> a)  Recompile your Java Application with a full JDK 7 compiler. You can 
>>> test it with the GAE 1.7.5 SDK, and when ready, use the regular appcfg SDK 
>>> tool that will detect that the Java byte code is Java 7 compliant and will 
>>> use a Java7 runtime for this application version.
>>>
>>> b)  If you are still compiling your Java application with a JDK 6 
>>> compiler, you can deploy to the Java 7 runtime by adding the *
>>> --use_java7* flag to the appcfg SDK tool.
>>>
>>> Please review the Google Java 7 
>>> Considerationspaper
>>>  for additional information on configuring Java 7. 
>>>
>>> 3.  Assuming you have your default application version still running 
>>> with a Java 6 runtime and a new version running in Java 7, you can use the 
>>> Google App Engine Traffic Splitting feature to slowly ramp up traffic on 
>>> the new Java 7 runtime.  Consider starting with 5%, then increase gradually 
>>> to 10%, 20%, and so on as your app is behaving as expected.  See our 
>>> Traffic 
>>> Splitting 
>>> documentfor
>>>  more information about this tool.
>>>
>>> Thanks for spending the time to make sure your application is Java 7 
>>> ready now. Only a very few incompatible behaviors may have to be fixed in 
>>> your applications. 
>>>
>>>