Tim Holloway wrote:
Finally, remember that if you're going to take the defaults on Tomcat deployment, the WAR has to be a named directory directly under TOMCAT_HOME/webapps. That is, TOMCAT_HOME/webapps/mywebapp/(the war files) is what you need. You cannot dump the files directly into TOMCAT_HOME/webapps. The WAR directory name will be used (by default) to construct the webapp's Context path.
Tim Holloway wrote:Then again, you might want to consider using something like Jenkins to make all of this a little easier.
Bear Bibeault wrote:You have no build process?
Tim Holloway wrote:If you are building a WAR file, keep building it. It originally sounded to me like you weren't doing that anymore.
Tim Holloway wrote:Maven is good because it encourages a standard project structure and you don't have to set up a complex chain of build rules - it already knows how to take a Maven-standard project and produce a target.
Tim Holloway wrote:Jenkins itself isn't really so much a build tool as a GUI-based build manager. I use it to run Maven-based builds. Among its virtues are that any authorized user can check the state of the project, including the test results, builds can be triggered automatically when code is checked in or on a regular schedule (if you are into nightly builds) and more.
Paddy spent all of his days in the O'Furniture back yard with this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton