2009/1/18 mcs130 <[email protected]> > > Hello, > > Can someone shed some light on the following. (I am not new to Web dev but > new to Maven). After running the following archetype: > > Struts 2 Basic mvn archetype:create > -DarchetypeGroupId=org.appfuse.archetypes > -DarchetypeArtifactId=appfuse-basic-struts > -DremoteRepositories=http://static.appfuse.org/releases > -DarchetypeVersion=2.0.2<http://static.appfuse.org/releases-DarchetypeVersion=2.0.2>-DgroupId=com.mycompany.app > -DartifactId=myproject > > I followed the following instructions to the letter: > > Check your new project into source control, unless you have a good reason > not to. Google Code has free Subversion hosting, as do many others. > From the command line, cd into your new project's directory and run mvn to > download JARs, Tomcat and run the integration tests in your project. Now is > a good time to take a coffee break or grab a beer - downloading everything > and running the tests can take 5-10 minutes. > To view your application run mvn jetty:run-war from your project's > directory > (for a modular project, you'll need to run mvn jetty:run-war from your > project's web directory). Maven will start Jetty and you should be able to > view your application in your browser at http://localhost:8080. > > The log messages scrolled for quite some time as it indicated it would > despite a number of errors thrown while it was doing something with Tomcat. > My preference would be to use Tomcat over Jetty anyway (but that is not my > question). What is confusing to me is: Why is Tomcat involved in all of > this if we have to run this mvn jetty:run-war command? In the end, the > application came up fine at localhost:8080, the database was created in > MySQL, and all seems ok. But (as was always my issue w/ Maven), I don't > like not knowing what all is going on w/ its auto downloading, installing, > and configuring things...Matt deserves a medal for all this effort for > sure. > There is so much stuff going on, however, it's confusing and this Tomcat > thing just added to it.
The integration tests use Cargo to load the application into Tomcat. I think several of the tests do test boundary conditions and may throw the odd stack trace. To confirm this do one of the following: 1) Look at the test results in target/surefire-reports 2) Run mvn site to build the site and look at the test reports in the site. mvn jetty:run-war is largely to aid the development cycle - it is not intended to be a production container, merely a quick and easy way to get the site up and running. Mike > > > Maybe there is a note or warning posted about this already, so forgive me > if > this is redundant. > > Thanks > > > -- > View this message in context: > http://www.nabble.com/Appfuse-Quickstart---mvn-command-runs-but-with-Tomcat-errors--Why--tp21523004s2369p21523004.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
