{"id":238,"date":"2026-10-13T01:10:51","date_gmt":"2026-10-13T01:10:51","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2010\/04\/14\/what-is-pom\/"},"modified":"2026-10-13T01:10:51","modified_gmt":"2026-10-13T01:10:51","slug":"what-is-pom","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/what-is-pom\/","title":{"rendered":"Maven POM Explained: Structure, Inheritance, and Practical pom.xml Examples"},"content":{"rendered":"\n

In Maven, pom.xml<\/strong> is the fundamental project descriptor: it defines your artifact identity, dependencies, plugins, and build behavior. This guide is for engineers who use Maven in CI\/CD or local builds and want a clear, practical understanding of how POM configuration is resolved and executed.<\/p>\n\n\n\n

Originally published on 2010-04-14; fully revised and updated.<\/em><\/p>\n\n\n\n

\"Maven<\/p>\n\n\n\n

What a POM is and what Maven uses it for<\/h2>\n\n\n\n

A Project Object Model (POM)<\/strong> is Maven\u2019s configuration model stored in pom.xml<\/strong>. When you run a Maven goal, Maven reads this file (from the current directory unless you pass -f<\/code>) and uses it to determine how to build your project.<\/p>\n\n\n\n

  • Project coordinates (groupId, artifactId, version)<\/li>
  • Packaging type (for example, jar, war, pom)<\/li>
  • Dependencies and dependency versions<\/li>
  • Build plugins and plugin configuration<\/li>
  • Profiles, repositories, metadata, and reporting settings<\/li><\/ul>\n\n\n\n

    Minimal POM: the required fields<\/h2>\n\n\n\n

    A minimal valid POM needs the project root plus these required elements: modelVersion<\/strong>, groupId<\/strong>, artifactId<\/strong>, and version<\/strong>. Together, groupId:artifactId:version form the artifact coordinates (GAV).<\/p>\n\n\n

    <project<\/span>><\/span>\n  <modelVersion<\/span>><\/span>4.0.0<\/modelVersion<\/span>><\/span>\n  <groupId<\/span>><\/span>com.mycompany.app<\/groupId<\/span>><\/span>\n  <artifactId<\/span>><\/span>my-app<\/artifactId<\/span>><\/span>\n  <version<\/span>><\/span>1.0.0<\/version<\/span>><\/span>\n<\/project<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
    If you do not declare packaging<\/strong>, Maven uses jar<\/strong> by default.<\/p>\n\n\n\n
    Common pom.xml sections in real projects<\/h2>\n\n\n\n
    Most production POM files add dependency management, plugin configuration, and Java\/toolchain properties. A practical skeleton looks like this:<\/p>\n\n\n
    <project<\/span>><\/span>\n  <modelVersion<\/span>><\/span>4.0.0<\/modelVersion<\/span>><\/span>\n  <groupId<\/span>><\/span>com.example<\/groupId<\/span>><\/span>\n  <artifactId<\/span>><\/span>orders-service<\/artifactId<\/span>><\/span>\n  <version<\/span>><\/span>1.0.0<\/version<\/span>><\/span>\n  <packaging<\/span>><\/span>jar<\/packaging<\/span>><\/span>\n\n  <properties<\/span>><\/span>\n    <maven.compiler.source<\/span>><\/span>17<\/maven.compiler.source<\/span>><\/span>\n    <maven.compiler.target<\/span>><\/span>17<\/maven.compiler.target<\/span>><\/span>\n  <\/properties<\/span>><\/span>\n\n  <dependencies<\/span>><\/span>\n    <dependency<\/span>><\/span>\n      <groupId<\/span>><\/span>org.slf4j<\/groupId<\/span>><\/span>\n      <artifactId<\/span>><\/span>slf4j-api<\/artifactId<\/span>><\/span>\n      <version<\/span>><\/span>2.0.0<\/version<\/span>><\/span>\n    <\/dependency<\/span>><\/span>\n  <\/dependencies<\/span>><\/span>\n\n  <build<\/span>><\/span>\n    <plugins<\/span>><\/span>\n      <plugin<\/span>><\/span>\n        <groupId<\/span>><\/span>org.apache.maven.plugins<\/groupId<\/span>><\/span>\n        <artifactId<\/span>><\/span>maven-compiler-plugin<\/artifactId<\/span>><\/span>\n      <\/plugin<\/span>><\/span>\n    <\/plugins<\/span>><\/span>\n  <\/build<\/span>><\/span>\n<\/project<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
    Super POM, parent POM, and project inheritance<\/h2>\n\n\n\n
    Maven applies inheritance in layers. Every project inherits from Maven\u2019s built-in Super POM<\/strong>. You can also define your own parent POM<\/strong> to standardize settings across multiple services or modules.<\/p>\n\n\n\n
    POM type<\/th>Who defines it<\/th>What it controls<\/th>Typical use<\/th><\/tr><\/thead>
    Super POM<\/td>Maven<\/td>Built-in defaults and baseline behavior<\/td>Implicit base for all Maven projects<\/td><\/tr>
    Parent POM<\/td>Your org\/team<\/td>Shared plugin versions, repositories, dependency management, policies<\/td>Standardizing many projects<\/td><\/tr>
    Project POM<\/td>Individual project<\/td>Service-specific dependencies and build config<\/td>Application-level customization<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Commonly merged\/inherited areas include dependencies, plugin lists, plugin configuration, resources, and (with matching IDs) plugin executions.<\/p>\n\n\n
    <project<\/span>><\/span>\n  <parent<\/span>><\/span>\n    <groupId<\/span>><\/span>com.example.build<\/groupId<\/span>><\/span>\n    <artifactId<\/span>><\/span>platform-parent<\/artifactId<\/span>><\/span>\n    <version<\/span>><\/span>1.0.0<\/version<\/span>><\/span>\n  <\/parent<\/span>><\/span>\n\n  <modelVersion<\/span>><\/span>4.0.0<\/modelVersion<\/span>><\/span>\n  <groupId<\/span>><\/span>com.example.services<\/groupId<\/span>><\/span>\n  <artifactId<\/span>><\/span>billing-service<\/artifactId<\/span>><\/span>\n  <version<\/span>><\/span>1.2.3<\/version<\/span>><\/span>\n<\/project<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
    How Maven resolves and executes POM configuration<\/h2>\n\n\n\n
    The build configuration Maven actually executes is the effective POM<\/strong> (project POM + parent POM + Super POM + active profiles).<\/p>\n\n\n\n
    \nflowchart TD\n    A[Run mvn goal] --> B[Read project pom.xml]\n    B --> C[Resolve parent POM]\n    C --> D[Apply Super POM defaults]\n    D --> E[Build effective POM]\n    E --> F[Resolve dependencies and plugins]\n    F --> G[Execute lifecycle phase and goal]\n<\/pre>\n\n\n
    # Build using pom.xml in current directory<\/span>\nmvn clean package\n\n# Build with a specific POM file<\/span>\nmvn -f .\/path\/to\/pom.xml clean verify\n\n# Inspect the final merged configuration Maven sees<\/span>\nmvn help:effective-pom<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Best practices and common pitfalls<\/h2>\n\n\n\n
    • Keep coordinates stable and meaningful; changing groupId\/artifactId impacts dependency consumers.<\/li>
    • Centralize shared versions and plugin defaults in a parent POM for consistency.<\/li>
    • Use mvn help:effective-pom<\/code> when inheritance or profiles produce unexpected behavior.<\/li>
    • Avoid duplicating plugin versions across many child projects.<\/li>
    • Be explicit about repository usage and avoid unnecessary custom repositories when possible.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
      The Project Object Model (POM) is Maven\u2019s central configuration file and the source of truth for how a Java project is built. This guide covers required fields, inheritance (Super POM and parent POM), and how Maven creates the effective build configuration.<\/p>\n","protected":false},"author":1,"featured_media":4279,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[3895,3897,3877,3900,3901,3893,3894,2339,3899,3898,719,3896,3892],"class_list":["post-238","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorised","tag-about-pom","tag-minimal-pom","tag-pom","tag-pom-guide","tag-pom-in-maven","tag-pom-introduction","tag-pom-overview","tag-project","tag-project-inheritance","tag-project-object-model","tag-start","tag-super-pom","tag-what-is-pom"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/238","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=238"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/238\/revisions"}],"predecessor-version":[{"id":79068,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/238\/revisions\/79068"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/4279"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=238"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=238"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=238"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}