a) Create a parent POM that includes all of those JARs as dependencies and then have each of your project declare that parent POM.
b) Create a stand-alone POM that declares all of those JAR as dependencies and then include that POM as a dependency in all of your projects.
I usually use option (a) - essentially what you are doing is defining a POM for a type of web application; and then all web applications of that type use that POM as the parent POM. I usually find it handy to have a parent POM for each application type that I will be creating, and in some cases I use a hierarchy of parent POMs, each one adding additional functionality. For example, my root POM has only licensing information and the URL for my employer. Then I have separate sub-POMs for various different application types, some of which add dependencies, others of which add plugins (for example, for building the javadoc and source jars), and then others that are more focused on specific project types (for example, all Spring MVC projects have a common parent POM).