Using Profiles in Maven
Using Profiles in Maven One of Mavens many advantages is the ability to configure automated deployments. By configuring the Maven POM, we can set a Web Archive (WAR) deployments to a given JEE Server (e.g. Tomcat, Liberty Core, etc). Most projects involving more than one developer have some concept of a deployment path. A deployment artifact is likely deployed on a local web server (DEV), then deployed on an integration server (INT), and promoted to a test server (QA) if a smoke test passes. We can configure each environment in the deployment path within our POM file. Typically, the POM file for a Tomcat deployment would contain a section that looks something like this: <plugin> <groupId> org.apache.tomcat.maven </groupId> <artifactId> tomcat7-maven-plugin </artifactId> <version> 2.2 </version> <configuration> <url> http://localhost:8080/manager/text </url> <server> TomcatServer </server> <pat...