have a look at the jetty:run and tomcat:run mojos... these will package up the war files into a directory, start a jetty or tomcat container respectively and serve the webapp in place, The jetty one supports scanning of the source files and automatic reloading of the webapp... I think the tomcat one might support the same, but I'm not sure.
These mojos make CLI development trivial IMHO 2009/2/13 Lee Goddard <[email protected]>: >> I think it is the case that most people who use Maven will be >> using a Java IDE of some sort. These take care of ensuring >> that the right files are seen by the web server at the right time. > > I feared as much. > > >> Generally, though it's fairly normal (when outside of an IDE) >> to package the software before letting tomcat (or any other servlet >> container) at it. > > But not during development, surely? When actually writing the files? > >> If you really want tomcat to serve your files directly, you >> can configure it (in conf/Catalina/localhost/myproj.xml) to >> point directly at .../myproj/src/main/webapp. I'd say that >> this isn't a particularly normal usage scenario though. > > So I'll probably try to avoid it. > > Thanks for your help. > > I got the impression that Maven is intended to be used from the start of > coding on a project, but it doesn't seem to sit very well with > non-IDE-based development. > > Is there no parallel case in Maven for the Ant model of copying files > from a source tree to a build location, as outlined in the Tomcat > Developer's Guide on the Apache Tomat homepage? > > http://tomcat.apache.org/tomcat-6.0-doc/appdev/processes.html > > Thanks again, > Lee > > http://www.bbc.co.uk/ > This e-mail (and any attachments) is confidential and may contain personal > views which are not the views of the BBC unless specifically stated. > If you have received it in error, please delete it from your system. > Do not use, copy or disclose the information in any way nor act in reliance > on it and notify the sender immediately. > Please note that the BBC monitors e-mails sent or received. > Further communication will signify your consent to this. > > > --------------------------------------------------------------------- > 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]
