I'm successfully using Eclipse 3.1.2, WTP 1.0.1, Tomcat 5.0.28, and Maven 2 to do the full end-to-end (as long as you don't mind running Maven from the command line) for webapps.
I can answer questions at a much slower rate for free on the mailing list, but that's it. :) -Stephen On 3/13/06, Hines, John <[EMAIL PROTECTED]> wrote: > Last year, I supported a maven 1.0 build process written by someone else > that creates a web app as an ear. It was used by our coders, mostly > short term contractors who know nothing about the build process except > to run scripts. The methodology was developer: > ...creates or edits and compiles a file/several files on Windows > ...ftp the file/files to his server instance on a unix box > ...run a build script then a deploy script and > ..tests on his unix instance of JDK 1.4/WebLogic 8.1. > > Late last year I was able to "clone" the unix build and deploy scripts > into windows batch files. The batch files were a little clunky but the > process worked so now the developer can do everything on a windows box. > (Why? Because everybody's got one.) > > I then looked into doing everything in Jbuilder 2005 (our > quasi-corporate standard) with MavenIDE but decided I wasn't smart > enough to make it happen. (I'd prefer to say that Maven 1.0 and > MavenIDE for JBuilder on Windows didn't work very well but I'm perfectly > happy if anybody wants to argue I was too dumb to make it work.) > > Anyway, now JBuilder is dead and I've learned enough Eclipse 3.1 to > think I might be able to make things work in Eclipse. > > Question 1: Is anybody doing end to end web app development > (edit/build/deploy/test/debug) on Windows using Eclipse 3.1/WTP 1.0 and > Maven IDE? If so, what version JDK, what web server/web server version > and what maven version? > > Question 2 (assumes "yes" to Question 1): > > Given: Windows XP SP 1 or 2 w/1GB memory and big drive,, JDK 1.4.2_05, > Eclipse 1.3 with WTP 1.0 , WebLogic 8.1 SP3. (That's all non-negotiable > except the wtp part is probably negotiable) And knowing I have a > boatload of inherited Maven 1.0.2 jelly and xml files and windows batch > files that build and deploy an ear to WebLogic on Windows. > > Assuming: my goal is give every developer a written procedure and zip > file that will allow him to create a "standard" instance with JDK > 1.4.2_05, Eclipse 3.1 with Web Tools Platform 1.0, some version of Maven > and MavenIDE and WebLogic 8.1 SP3 where he can do end-to-end code, > build, debug without leaving Eclipse 3.1, what's the LEAST PAINFUL thing > to do to get things working by April Fool's Day: > > 1. Slit my wrists; > 2. Stay with Maven 1.0.2 and Maven IDE for Eclipse and modify the > existing windows batch, jelly and xml files; > 3. Move to Maven 1.1 and Maven IDE for Eclipse and modify the existing > windows batch, jelly and xml files; > 4. Move to Maven 2.0 and drink lots of Jolt and don't sleep. > > Question 3: (Assuming 2, 3 or 4 to Question 2) Anybody what has > already done this want to make $50/hr (paid in advance by paypal out of > my pocket--it's a chance to learn something new) answering stupid > emails? > > Thanks in advance, John Hines [EMAIL PROTECTED] aka "No one of > consequence" > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
