GPE facets with modules

I've got it working ok now. I deleted that error in the first screenshot (below 
in my original email) and it hasn't reappeared. 

Also weird is just that there is two GAE facet's to choose from:

http://take.ms/L4Lunq
http://take.ms/xovkC7

jon

On Mon, Aug 19, 2013 at 12:17 PM, Rajeev Dayal <rdayal@google.com> wrote:
Hey Jon,

I think you've basically identified a bit of a problem that we've exposed by 
putting out the Modules support. It's basically interfering with our existing 
Maven support, which used to work with imported Maven projects.

Here's a summary of how things used to work before we added Module support:

If you had GPE installed, and the m2e connector for WTP projects (which is now 
included by default in Eclipse 4.3), then we'd automatically add the App Engine 
nature (not facet) and set the App Engine SDK to point over to an unpacked 
version in your .m2 directory. A caveat to this is that you need to be using 
the maven-gae-plugin in your pom.xml; this logic was never updated to work with 
the appengine-maven-plugin (this is something that we need to fix immediately) 

Now that we've added Module support, if you have a Maven project, and you 
import it into GPE, you'll still get the same behavior as above. Though you can 
add the App Engine facet, it would not recommend that right now, because you're 
going to get confusing behavior as a result. You'll get into the state where 
your project has both the App Engine nature and the App Engine facet, which is 
somewhat undefined. So, for now, if you're importing a Maven project into GPE, 
do not enable the App Engine facet.

After we get Cloud Endpoints support working, we're going to have to 
concentrate on the Maven functionality. The way this should work is that when 
you import a Maven project that uses the appengine-maven-plugin, GPE should 
automatically add the App Engine facet for you (and NOT add the App Engine 
nature). We should probably do some cleanup here too to remove the App Engine 
nature if it happens to be set on the project.

Do you mind filing a bug about this so that I can mention the details there and 
we can discuss further as needed?

Thanks,
Rajeev

On Thu, Aug 15, 2013 at 1:41 PM, Rajeev Dayal <rdayal@google.com> wrote:
+[amitin, ludo]

On Thu, Aug 15, 2013 at 12:58 AM, Jon Stevens <latchkey@gmail.com> wrote:
Hey Rajeev, 

I added the Google AppEngine facet to my webapp/war project and now I get this 
error...

http://take.ms/cpV49

For the runtime, I only have the default runtime that is included with the GPE 
plugin. Nowhere do I specify the maven repo path except in my pom.xml files, 
which seems kind of necessary.

http://take.ms/vTXvf
http://take.ms/lu1zor

Also, when I added the facet, it defaulted the webapp gae version to 1, when I 
had it set to 'snapshot'. It also setup some default files (a servlet, html 
page and some config) which I didn't want since this is adding the facet to an 
existing project.

By the way, I know this stuff isn't production ready, but at the same time, I'm 
kind of stuck since it is the only way to use GPE with Maven.

Thanks for your help,

jon
Original issue reported on code.google.com by latch...@gmail.com on 20 Aug 2013 at 2:24
dgallen / google-plugin-for-eclipse

GPE facets with modules #231
