Re: Maven users survey

Hello,
I know, this is GWT thread, but as I understand you are on Google
Plugin for Eclipse team,
so I assume, I can bother you regarding both GWT and GAE.

The problem with gwt-maven-plugin is that when running GAE project
locally, as described by other people above,
GAE is not initialized and persistence doesn't work.

Follow these instructions to create GAE project using maven-gae-plugin
(http://maven-gae-plugin.googlecode.com):

1. Create project:

mvn archetype:create -DarchetypeGroupId=net.kindleit -
DarchetypeArtifactId=gae-archetype-gwt -DarchetypeVersion=0.5.0 -
DgroupId=net.kindleit -DartifactId=maven-gae-example -
DremoteRepositories=http://maven-gae-plugin.googlecode.com/svn/
repository

Next commands must be run from project's root directory (type "cd
maven-gae-example")

2. download and unpack GAE SDK to your repository (You need to do this
only once.. Also we are now working on automating this step):
mvn gae:unpack

3. create Eclipse project files:
mvn eclipse:eclipse

After this you should be able to Import your project in Eclipse.

The problem is that trying to enable Google Plugin for Eclipse on this
project fails.
If you'd manage to patch the Google Plugin, so everything works fine -
all Maven users would be happy :)

More commands:

4. building and running the project locally:
mvn package gae:run

(you can also use "gae:debug" instead of "gae:run" for running in
debug mode)

5. deploying project to appspot:
mvn gae:deploy

P.S. I've also tried to set up project with war directory in project
root, but run into some weird errors:
http://groups.google.com/group/maven-gae-plugin/browse_thread/thread/497e2dd1ee252650

On Jan 13, 6:35 pm, Keith Platfoot <kplatf...@google.com> wrote:
> Hi folks,
>
> For the next release of the Google Plugin for Eclipse, we're planning on
> making a few tweaks to make life easier for Maven users. That's right: we've
> seen the stars on the issue tracker, and have decided it's time to act. I
> would say, "we feel your pain", but the problem is, we don't. Which is to
> say, nobody on the plugin team actually uses Maven (everybody around here
> uses Ant). However, I've been researching Maven to determine exactly what
> changes we should make to allow it to work more seamlessly with the Google
> Eclipse Plugin. I've read the relevant issues and groups postings, so I
> think I have a rough idea of what needs to happen. However, before we go and
> make any changes, I wanted to ask for the community's advice.  So, here are
> some questions for you.
>
> What is the typical workflow of a GWT developer using Maven?
>
> I've installed Maven and the gwt-maven-plugin 1.2-SNAPSHOT and managed to
> create a GWT 2.0 app with the provided archetype. After some tweaking, I'm
> able to GWT compile, debug with Eclipse (though not via our Web App launch
> configuration), create a WAR, etc. However, I'm more interested in how you all
> are doing things. For example:
>
> How do you...
>
>    - Create a new project?
>    - Perform GWT compiles?
>    - Debug with Eclipse?
>    - Run your tests?
>    - Create a WAR for deployment?
>
> What specific pain points do Maven users run into when using the Google
> plugin?
>
> I know one major obstacle is that our plugin currently treats the war
> directory as both an input (e.g. static resources, WEB-INF/lib,
> WEB-INF/web.xml) and output (WEB-INF/classes, GWT artifacts like nocache.js
> and hosted.html) . Maven convention, however, says that /src/main/webapp
> should be input only, which means that hosted mode (or development mode, in
> GWT 2.0) needs to run from a staging directory (e.g. gwt:run creates a /war
> folder on demand). This mismatch results in the plugin creating spurious
> validation errors and breaks our Web App launch configuration.
>
> Another incompatibility is that Maven projects depend on the GWT Jars in the
> Maven repo, whereas our plugin expects to always find a GWT SDK library on
> the classpath.
>
> Are my descriptions of these pain points accurate?  If so, one possible
> solution would be for the plugin to allow the definition of an input war
> directory (e.g. src/main/webapp) separate from a launch-time staging
> directory, and for us to relax the requirement that all GWT projects must
> have a GWT SDK library.  So tell me: would these changes adequately reduce
> the friction between Maven and the Google plugin?
>
> Also, are there other problems Maven users are running into when using the
> plugin?
>
> Thanks in advance for all feedback,
>
> Keith, on behalf of the Google Plugin for Eclipse team