Export to GitHub

google-web-toolkit - issue #3584

Google Plugin for Eclipse Add WAR Export and EAR support


Posted on Apr 21, 2009 by Grumpy Ox

Found in GWT Release (e.g. 1.5.3, 1.6 RC): 1.6.4

Encountered on OS / Browser (e.g. WinXP, IE6-7, FF3): Eclipse

Detailed description (please be as specific as possible):

This is a feature request for the ability to export a Google "Web Application Project" as a WAR and for the ability to add this project to an EAR. Without these features it is a bit cumbersome working on applications that will be deployed on J2EE Application Servers and not the Google App Engine.

Workaround if you have one:

GWT Compile and copy the /war/ output into a standard Dynamic Web Project.

Links to relevant GWT Developer Forum posts: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/608c6f80cce0a9f9/39a0265b97634225#39a0265b97634225

Comment #1

Posted on Apr 22, 2009 by Grumpy Horse

Could be a useful feature to support. Passing onto Miguel for thoughts.

Comment #2

Posted on Apr 23, 2009 by Happy Cat

We do want to do WAR export as a feature. Could you provide more detail about what you mean by add this project to an EAR? (I want to make sure that I really understand where you are coming from).

Comment #3

Posted on Apr 23, 2009 by Grumpy Ox

Sure, usually when you create a standard eclipse dynamic web project it has an option titled "EAR Membership" with the choice to add the project to an EAR project (if the EAR project does not exist, it will create one and add it to the deployment descriptor)

The second face of the feature is that if I have an EAR project and I go via the deployment descriptor GUI to add a module, the dynamic web project I created is available while a "Google Web Application Project" is not.

Hope that helps.

Thanks a lot!

Comment #4

Posted on Apr 30, 2009 by Happy Bird

I believe these issues can be resolved by having the eclipse project generator output a 'faceted' project. This will allow the project to be exported as a WAR, or included in an EAR, using the default eclipse tools.

To do this: 1. the .project file needs to include the following natures: org.eclipse.jem.workbench.JavaEMFNature org.eclipse.jdt.core.javanature com.google.gwt.eclipse.core.gwtNature com.google.gdt.eclipse.core.webAppNature org.eclipse.wst.common.modulecore.ModuleCoreNature org.eclipse.wst.common.project.facet.core.nature (Actually I am not certain about the JavaEMFNature) The webAppNature corresponds to the Dynamic Web Project. Not sure what the EAR nature is, offhand.

  1. The Dynamic Web Project's web content folder needs to be changed from "WebContent" to "war", to align with the GWT's project layout. This can be accomplished by modifying the file .settings/org.eclipse.wst.common.component and changing to

This also provides some nice EclipseEE integration WRT running on a server, etc... See http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/39e0ff6325e4d504/55bfd342d77ec910#55bfd342d77ec910

Comment #5

Posted on May 1, 2009 by Quick Lion

Alex Rudnick suggested that I respond to this issue, because I had raised a similar issue in the GWT forum. Please see http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/4e8c8a46331484f6/0fd3300f62e0d5ba?hl=en#0fd3300f62e0d5ba.

You should see from the forum postings, that I cast an overwhelming vote for GWT to help developers with this issue.

Thanks,

Danny Danny

Comment #6

Posted on May 4, 2009 by Happy Cat

(No comment was entered for this change.)

Comment #7

Posted on Dec 21, 2009 by Happy Ox

(No comment was entered for this change.)

Comment #8

Posted on Feb 7, 2010 by Happy Hippo

Comment deleted

Comment #9

Posted on Jun 21, 2010 by Swift Giraffe

I would also suggest that it be possible to turn off the war folder requirement for those that wish to deploy to an external server. My eclipse setup includes an EAR project, Dynamic Web Project(WAR with Jersey Services), EJB project, and a GWT Project. It would be nice if the war folder and web.xml validation turned off for external deployments, or at least if you had it as an option.

Comment #10

Posted on Jan 13, 2011 by Swift Ox

(No comment was entered for this change.)

Comment #11

Posted on Mar 29, 2011 by Quick Giraffe

Would be solved if GWT Plugin would include something like a GWT Facet as we did as an experiment in JBoss Tools: http://community.jboss.org/docs/DOC-15794

Then GWT projects could use all of WTP's features for packaging/assembly instead of something different + it would work with m2eclipse/WTP integration too.

Comment #12

Posted on Oct 5, 2011 by Swift Ox

(No comment was entered for this change.)

Comment #13

Posted on Mar 7, 2012 by Massive Giraffe

As an eclipse developer, I just start learning GWT. An export to war wizard is very helpful, but I didn't find it in GDT. I put together a small plugin quickly at http://code.google.com/p/gwt-project-export-wizard/. It doesn't depend on any WTP plugins which makes it small.

Comment #14

Posted on Apr 16, 2013 by Massive Cat

moved to google plugin for eclipse issue tracker: https://code.google.com/p/google-plugin-for-eclipse/issues/detail?id=121

Comment #15

Posted on Feb 22, 2015 by Happy Lion

i am facing a problem while plugin for GWT in eclipse problem is this

Unable to connect to repository https://dl.google.com/eclipse/plugin/4.3/content.xml Unable to connect to repository https://dl.google.com/eclipse/plugin/4.3/content.xml Connection to http://proxy6.bhu.ac.in:443 refused

please let me know how solve this

Status: Invalid

Labels:
Category-EclipsePlugin Priority-High Type-Feature