When assessing the two solutions, reviewers found Apache Tomcat easier to use and set up. However, Apache Maven is easier to administer. Reviewers also preferred doing business with Apache Maven overall.
The most important things about maven is it's project management. It can manage a really really big project without any problem. I am using maven for almost every project I am doing currently. I feel that maven is extremely powerful for software project...
1. The worst think about maven is the documentation. Not everything is written out in plain text, it takes a lot to really 'master' maven and maven 3 is even large. 2. If something fails. maven will give you cryptic error messages. The life-cycle concept...
I mostly like the ease of deployment of a Web application in Apache Tomcat. We can easily upload a war file through Tomcat manager UI or directly upload the war file in webapps folder thru an FTP.
Tomcat is often hard to diagnose when issues arise.
The most important things about maven is it's project management. It can manage a really really big project without any problem. I am using maven for almost every project I am doing currently. I feel that maven is extremely powerful for software project...
I mostly like the ease of deployment of a Web application in Apache Tomcat. We can easily upload a war file through Tomcat manager UI or directly upload the war file in webapps folder thru an FTP.
1. The worst think about maven is the documentation. Not everything is written out in plain text, it takes a lot to really 'master' maven and maven 3 is even large. 2. If something fails. maven will give you cryptic error messages. The life-cycle concept...
Tomcat is often hard to diagnose when issues arise.