Skip to main content

Home/ Google AppEngine/ Group items tagged plugin

Rss Feed Group items tagged

Esfand S

Extending Entity to provide real POGO like qualities with names attributes - Gaelyk | G... - 0 views

  • 1) Show the plugins.groovy and routes.groovy files in the WEB-INF folder in the Gaelyk project diagram. They are currently absent from the diagram. 2 Put a star or some other icon next to the mandatory plugins folder and the 2 mandatory plugin files (plugins.groovy and the plugin descriptor file) in the diagram. This will help show that one just needs to mix in in these files with the rest of their own project's files.
Esfand S

maven-gae-plugin - Allow maven-gae-plugin to be used for integration tests - 0 views

  • 3. Adds a new gae:start goal. This is identical to gae:run, except that it does not automatically execute the package phase before starting the server. The intent is to use this in a project POM, but it can also be used to start the server quickly when you don't want to rebuild the project. Right now I just copied the RunGoal completely, except for the '@execute phase="package"' declaration, because I didn't want to introduce conflicts in case someone else is editing RunGoal.java. A better thing to do in the future would be to have RunGoal extend StartGoal with an empty class that just adds the '@execute phase="package"' annotation (it can't be the other way around, with StartGoal extending Run goal, because there's no way to override a mojo with an @execute annotation with one that doesn't have it---it gets inherited automatically).
  • The idea behind all of these changes is to make it so that you can use the maven-gae-plugin in a project's POM for automated integration tests. The gae:start goal automatically binds to the pre-integration-test phase by default, and the gae:stop goal binds to post-integration-test. This is most useful when combined with something like the maven-failsafe-plugin and a functional testing library like HtmlUnit that you can use to simulate web requests. It would also be useful for Selenium testing.
Esfand S

FAQ - Google Plugin for Eclipse - Google Code - 0 views

  •  
    "How do I use the plugin with a GWT project built with Maven? Although GWT projects typically use the Ant build system, it is also possible to use GWT and the Google Plugin for Eclipse with projects built with Maven. We recommend using Eclipse for Java EE when developing Maven projects, because it allows you to modify your source code and resources during a debugging session and have the changes automatically reflected in your running application. To enable this behavior, you'll need to convert your Maven project to an Eclipse Dynamic Web Project: 1. Open the New Dynamic Web Project wizard. Set the Project name and any applicable options, then click Next. 2. On the Java page, remove the default source folder (src) and add your Maven source folders (e.g. src/main/java, src/main/resources, and src/test/java). Click Next. 3. On the Web Module page, set the Content directory to src/main/webapp and click Finish. 4. Import your project's source code and resources into the newly-generated project, and set up your build path. 5. Finally, follow the steps in the GWT + Eclipse for Java EE FAQ to enable GWT for the project and create a Web Application launch configuration."
Esfand S

Google App Engine in Maven + IntelliJ « Nelz's Blog - 0 views

  • build-time substitution. Here’s our appengine-web.xml: <?xml version="1.0" encoding="utf-8"?> <appengine-web-app xmlns="http://appengine.google.com/ns/1.0"> <application>${gae.app.name}</application> <version>${friendlyversion}</version> <system-properties> <property name="java.util.logging.config.file" value="WEB-INF/logging.properties"/> </system-properties> </appengine-web-app>
  • At build time, I use the AntRun plugin (lines 97-118) to create a small file under the target directory that holds a ‘sanitized’ version of the standard Maven version. (I.e. “1.0-SNAPSHOT” becomes GAE-friendly “1-0-snapshot”.) I then use the Maven filter functionality available in the WAR plugin (lines 80-96) to copy the appengine-web.xml into its proper directory with the version substituted in.
Esfand S

Tips for Getting Google App Engine to Operate in a Maven Environment - 0 views

  • To get the development environment working the plugin also requires access to the unzipped SDK as packaged by Google. The plugin tries to help you set this up (“gae:unpack”) but that failed for me. I was able to get stuff working by manually unzipping the SDK artifact downloaded directly from Google to the following directory: ~/.m2/repository/com/google/appengine/appengine-java-sdk/1.3.0/appengine-java-sdk-1.3.0
  • You’ll also notice in our appengine-web.xml that we substitute in our application name. By default this comes from the properties section of the pom.xml file (line 11).
Esfand S

Using the Google Plugin for Eclipse - Google App Engine - Google Code - 0 views

  • The war/ directory uses the WAR standard layout for bundling web applications. (WAR archive files are not yet supported by the SDK.) The Eclipse plugin uses this directory for running the development server, and for deploying the app to App Engine. When Eclipse builds your project, it creates a directory named classes/ in war/WEB-INF/, and puts compiled class files here. Eclipse also copies non-source files found in src/ to war/WEB-INF/classes/, including META-INF/ and the log4j.properties and logging.properties files. The final contents of the war/ directory make up your application for testing and deployment. For details about the new project that the plugin creates, see the Getting Started Guide.
Esfand S

Extending Entity to provide real POGO like qualities with names attributes - Gaelyk | G... - 0 views

  • a plugin is just a bunch of files as is accurately described in the docs and these files go in certain places in your application's folders in order to be used as is also accurately described in the docs.
Esfand S

Google Web Toolkit Blog: How to Use Google Plugin for Eclipse with Maven - 0 views

  • to enable both Maven and GPE for the same project. This article explains how to do that.
  • Mavenizing an existing GPE project To use Maven with an existing GPE project, follow these steps:
1 - 20 of 30 Next ›
Showing 20 items per page