Question

I am converting an application from Flex to Javascript. My workflow within Eclipse for Flex was to use Maven to start my Java web app in Tomcat and then have Eclipse configured to compile edited Actionscript files to a SWF and save it to my exploded WAR directory (that Maven/Cargo uses).

It worked very well for a long time allowing me to edit actionscript source code, flip over the browser, refresh the screen and see the changes.

I am new to Javascript however, and am struggling to get the same workflow up and running. The part I don’t understand is how to tell Eclipse that I would like my edited Javascript files to be written out to a particular directory (that contains the exploded WAR). In my WAR project (a WTP dynamic web project) there is something that looks like a Javascript build path called “Javascript resources”, but there is no output directory.

I would really like to continue to run Tomcat and Jetty via Maven if at all possible. I realize I can do what I want via WTP (M2E-WTP), but would prefer to use Maven/Cargo.

Answer 1

Denis’s suggestion to create custom builder is probably best solution if you want to continue using pure Maven/Cargo approach with Eclipse.

If you are deploying to an exploded war directory, then another similar idea would be to use a File Synchronization plugin. These will automatically copy modified files to configured folders. See:

• http://andrei.gmxhome.de/filesync/
• https://wiki.onehippo.com/display/CMS7/Use+Filesync+Eclipse+plugin+for+faster+turn+around

————-

FWIW, I don’t think Maven:Tomcat/Cargo plugins are ideal for real-time web development, especially on the frontend side of things. They are useful mainly for controlled deployments or bootstrapping a server without initial setup. My thoughts:

Eclipse WTP used to be great for real-time web development, but I stopped using it a few years back as it just got way too hard to make it work correctly in a Maven environment. Fwiw, my preferred approach these days looks like this:

• Do not install or use Eclipse WTP.
• Use m2eclipse to integrate Maven with Eclipse.
• Use Maven to do clean builds and generate exploded WAR directory in target folder.
• Setup independent Tomcat server to load webapp from the exploded target folder.
  • I suspect the tomcat setup/startup could be integrated into Maven. It’s not worth the extra complexity to me though.

Then, I configure JRebel (automatically via Maven) to handle java and web resource file changes. With this setup, I almost never have to redeploy or restart Tomcat. All changes (java, html, js, etc.) are seen immediately.

I think the same setup could be used without JRebel (for non-java files only) by configuring the web source folders as source folders in Eclipse with custom target output path being the corresponding directory in the exploded war directories. If that didn’t work, then it would definitely work by using the custom builder or file synchronization solutions mentioned above.