Sorry, I failed to mention that I run $ant dist prior to running Tomcat.
-- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx ----- Original Message ----- From: "James Mitchell" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Monday, June 28, 2004 8:46 AM Subject: Re: nominate ? > I can sympathize. > > Our build/test process for Struts is pretty complex, and began (i think) > while maven was just a twinkle in someone's eye;) At this point, I (just me > talking) am ignoring the Maven side of things for now. Our Maven setup > comes no where close to what the regular ant build script does. So if you > want to go that route for building/testing, that is what I (and I'm sure > others) are doing. > > Here's a very brief overview of what I do: > I use Eclipse to get the latest from CVS, and setup the project with only > the following for source paths: > /src/share > /src/test > /src/examples > /src/example > > I tell Eclipse to build to (default output folder): > /target/example/WEB-INF/classes/ > > If I want to test things in Tomcat, I add this at the bottom of the > server.xml (just above the ending </Host>) > > <Context path="struts-example" > docBase="D:/home/jmitchell/cvs/jakarta-struts/target/example" debug="0"/> > <Context path="struts-examples" > docBase="D:/home/jmitchell/cvs/jakarta-struts/target/examples" debug="0"/> > > I use cygwin, like so: > $ cd /cygdrive/d/home/jmitchell/apache_home/jakarta-tomcat-5.0.25/bin > $ ./catalina.sh jpda start > $ tail -f ../logs/catalina.out > > This allows me to debug (hot replacement and everything) the app so I can > try new stuff without the 5 minute wait for Ant to rebuild/redeploy. > > I have to change the output folder for the project to run one example app or > the other. I'm sure there is a better way to do that, but it works for me. > > Maven disadvantages (to me) > From a 'nurturing the community' perspective, the cost of 'converting' vs. > the cost of 'starting from scratch' can be more than we can afford right > now. We seemed to have a lot more participation before the attempt to > Mavenize began. > > I know I've found myself in several "states of mind" (if you will) when > considering making changes/patches: > - I don't want to make changes that could break the Maven build. > - I know how to do foo in Ant, but what is the Maven equivalent? > - If I add something to the Maven build process, will I get it correct on > the Ant side? > > I absolutely HATE the feeling of intimidation by my lack of knowledge of the > toolset and rather than pull my hair out learning yet 'another neat tool' > (pun indented) I (like others I'm sure) find myself fading into the > background and do simple things here and there where I can. > > Maven advantages (to me) > To Maven's credit, the concept is simply brilliant. You create a single (or > shared as commons does) config file(s) and all of a sudden, you can "build > from scratch" in 2 minutes instead of an hour, which is about what it takes > if you have to manually download and setup jar references, etc). Lately, I > am "getting to know" Maven over on jakarta-commons-sandbox/resources. > > As detailed above, Maven acceptance seems easier (to me) if the project was > created with Maven in mind. No special hacks or workarounds are needed. It > seems straight-forward and simple. > > > Thanks for letting me vent ;) > > -- > James Mitchell > Software Engineer / Open Source Evangelist > EdgeTech, Inc. > 678.910.8017 > AIM: jmitchtx > > ----- Original Message ----- > From: "Mark Lowe" <[EMAIL PROTECTED]> > To: "Struts Developers List" <[EMAIL PROTECTED]> > Sent: Monday, June 28, 2004 4:59 AM > Subject: Re: nominate ? > > > > Give me some pointers on building struts with all that maven gumph and > > I'd get involved with patch submission. I just haven't had the silly > > amount of time required to configure everything. Maven is installed, > > and I've the source checked out. Point me to some clear instructions on > > how to get the f&^%er built and I'd gladly pitch in. Regrettably the > > building struts had become more difficult than submitting patches. > > > > Mark > > > > On 27 Jun 2004, at 20:02, Vic Cekvenich wrote: > > > > > There are knowledgeable people currently active on user list, people > > > that wrote books, tutorials and papers, people that are writing > > > frameworks and extensions on Struts, should you want more activity, if > > > the current commit-ers are busy. > > > It's the right thing to do, I can think of about 10 one could > > > nominate, this would increase the patch activity I think. At least one > > > could start nurturing people. Many people active in the past are not > > > active now, such as David W. > > > Also, I know current developers don't think so, but * preception* is > > > that patches get ignored. > > > > > > .V > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
