Maven Concepts: Difference between revisions
Line 53: | Line 53: | ||
=Lifecycle= | =Lifecycle= | ||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[Maven Concepts - Lifecycle|Maven Lifecycle]] | |||
</blockquote> | |||
=System Properties= | =System Properties= |
Revision as of 01:06, 31 May 2016
Internal
POM
Profile
A profile is an alternative set of configurations which set or override default values. Profiles allow to customize a build for different environments. Profiles can be defined:
- per project in the pom.xml file
- per-user in ${user.home}/.m2/settings.xml
- global in ${maven.home}/conf/settings.xml
Each profile is identified with an identifier. Profiles customizes the build for different environments (e.g. production or development, different operating systems, different JDK versions, etc.)
An example of profile:
... <profiles> <profile> <id>production</id> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <debug>false</debug> <optimize>true</optimize> </configuration> </plugin> </plugins> </build> </profile> </profiles> ...
The profile can be activated explicitly on command line with -P:
mvn -Pproduction clear install
A profile can also be triggered through Maven settings, based on environment variables, OS settings, or present or missing files.
More information: http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Lifecycle
System Properties
System properties can be declared and exposed to the build in the <properties> section of pom.xml. See: