[google-appengine] Maven plugins

What is the difference between these two Maven plugins? - Based on the Google App Engine SDK for Java - com.google.*appengine*::appengine:appengine-maven-plugin - Older - Cloud-SDK Based

Re: [google-appengine] Maven plugins

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

Re: [google-appengine] Maven plugins

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 w

Re: [google-appengine] Maven plugins

*On Tue, May 9, 2017 at 6:10 PM, Brian de Alwis > wrote: * > 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 pl

Re: [google-appengine] Maven plugins

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 havin

Re: [google-appengine] Maven plugins

On Thu, May 11, 2017 at 5:01 AM, Brian de Alwis wrote: > 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