Build Profile in Maven and its Types

Triggering Build Profiles in Maven

There are various ways to trigger a Build Profile in Maven:

• Command-line interface.
   
• By means of Maven settings.
   
• Depending on environmental factors.
   
• OS configurations.
   
• Existing or missing files.

Build Profile Activation

In the Maven settings, profiles can be made active under the <activeProfiles> section. A list of <activeProfile> elements with a profile id within each profile is passed to this section.

The Syntax is as follows:

<settings>
  ...
  <activeProfiles>
    <activeProfile>Coding_Ninjas_profile-1</activeProfile>
  </activeProfiles>
  ...
</settings>

The profile contains an "activation" section describing these triggers. Currently, this detection is only capable of determining the JDK version prefix, whether a system property is present, and its value. Here are some illustrations.
 

When the JDK's version begins with "1.6," the settings listed below will activate the profile.

<profiles>
  <profile>
    <activation>
      <jdk>1.6</jdk>
    </activation>
    ...
  </profile>
</profiles>

When the system property "environment" is specified with the value "compile," the following example will cause the profile to be activated:

<profiles>
  <profile>
    <activation>
      <property>
        <name>environment</name>
        <value>compile</value>
      </property>
    </activation>
    ...
  </profile>
</profiles>

Build Profile Deactivation

There are various ways to activate profiles, but occasionally, we need to disable one. We can disable a profile with the '!' or '-'.

mvn groupId:artifactId:goal -P !Coding_Ninjas_profile-1,!Coding_Ninjas_profile-2,!?Coding_Ninjas_profile-3

OR

mvn groupId:artifactId:goal -P -Coding_Ninjas_profile-1,-Coding_Ninjas_profile-2,-?Coding_Ninjas_profile-3

Profiles tagged as activeByDefault or profiles that their activation config would otherwise activate can be deactivated using this method.

Must Read Apache Server

Frequently Asked Questions

What is POM in Maven?

POM stands for Project Object Model. Maven's basic unit of work is called a POM. It is an XML file with details about the project's config that Maven will use to build the project. The POM includes details about the project and different configuration settings that Maven uses to build the project (s).

How many types of Build Profiles are there?

There are three types of Build profiles in Maven. Per project, Per profile and Global Build profile. There is one more build profile i.e., Profile Descriptor. A profile descriptor is defined in project basedir (profiles.xml) but is not supported in Maven 3.0 and above.

How many Maven Build LifeCycles are there?

There are three maven-build lifecycles. These are default, clean and site lifecycles. The default lifecycle handles the deployment of your project. The clean lifecycle handles your project's cleanup. The site lifecycle handles the setup of your project's website.

Conclusion

We discussed the Maven Project Object Model. We discussed the uses of POM in Maven and the config details of the POM. Further, we discussed the minimum requirements of POm along with an example. We also covered some additional elements of the pom file.

We hope this blog has helped you. We recommend you visit our articles on different topics of Maven, such as

🔥 What do you mean by Maven?

🔥 Maven Configuration Properties.

🔥 Introduction to Maven Commands.

ping command in linux

If you liked our article, do upvote our article and help other ninjas grow.  You can refer to our Guided Path on Coding Ninjas Studio to upskill yourself in Data Structures and Algorithms, Competitive Programming, System Design, and many more!

Head over to our practice platform Coding Ninjas Studio to practice top problems, attempt mock tests, read interview experiences and interview bundles, follow guided paths for placement preparations, and much more!!

Happy Reading!!