Hi Keith,
basically my issues re described here:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/de0941a7c657c8f0/cbbf6292588041f8?#cbbf6292588041f8.
1. We have gwt as a maven 2 project where you can find these plugins
in pom file. Plus dependencies to other modules(ommited)
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>1.1</version>
<configuration>
<output>${basedir}/war</output>
<logLevel>INFO</logLevel>
<style>OBF</style>
<sourcesOnPath>true</sourcesOnPath>
<extraJvmArgs>-Xmx512m -Xss2048k</extraJvmArgs>
<runTarget>Project.html</runTarget>
<modules>
<module>com.project.Project</module>
</modules>
<inline>true</inline>
</configuration>
<executions>
<execution>
<goals>
<goal>compile</goal>
<!-- <goal>generateAsync</goal> -->
</goals>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<configuration>
<tasks>
<delete dir="${basedir}/src/webapp/
drguirpm" />
<delete dir="${basedir}/src/webapp/
gxt" />
<copy todir="${basedir}/src/webapp">
<fileset
dir="$
{project.build.directory}/${artifactId}-${version}">
<exclude name="*gwt-tmp/"/>
<exclude name="*-aux/"/>
</fileset>
<fileset
dir="${basedir}/war">
<include name="gxt/**" />
</fileset>
</copy>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptors>
<descriptor>src/main/assembly/assembly.xml</
descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>attached</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
2. We use m2eclipse plugin (http://m2eclipse.sonatype.org/update/)
3. For importing GWT project to eclipse I choose Import Maven project
in eclipse. I get project set up with all possible maven dependencies
etc.
4. I have to mark project as GWT Project. Properties->Google->Web
toolkit-> Use google web toolkit. Then I can start project as GWT web
application. But with the result mentioned in my previous post.
5. We compile whole thing with maven 2, but as I said we are in phase
where we don't have some concrete routines for packing our GWT GUI
layer with our existing app(struts based). but I believe generated
pages and jar will be in the same web app package as other stuff - so
not as a special GWT web app.
6. In eclipse we just start Debug as Web application. (with all
libraries manually copied into war/WEB-INF/lib)
7. UNIT tests: We haven't come so far ;)
So far we learned gwt principles, we managed to integrate it with
spring, managed to integrate it into our existing struts GUI, managed
to build with maven etc. - so more like infrastructure tasks. Now we
want to use our existing modules with screens we created in GWT.
8. WAR for deployement: see 5.
So our major problem with GWT is that we have to copy all maven
dependencies manually to war/WEB-INF/lib in hosted mode. Quite a issue
for modules that changes quite often. Without this need, I believe, we
would consider GWT-maven integration as very good.
Hope you get an idea how do we work.
Regards,
milan
On Jan 13, 5:35 pm, Keith Platfoot <[email protected]> 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
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
