Where Super POM comes from configuration

Question

When I look at my efficient pom in Eclipse, I see a load of dependencies and a shortcut that says that this is our corporate super-pom, which should be part of every project.

I can’t really figure out where super pom comes into play in the config. I looked at my settings.xml in maven and it has lists for remote repositories and internal repositories - but it doesn't seem to be able to see the super-pom link anywhere.

This is a muliple maven project built from an internal archetype and the parent module has a parent artifact defined ... but when I look at the parent artifact, I still don’t see how the super-pomp plays.

Any advice is appreciated.

Hi

I am

Answer 1

Super pom is defined by the tag <parent>:

<parent>
  <groupId>com.mycompany</groupId>
  <artifactId>mvn</artifactId>
  <version>1.0.0-SNAPSHOT</version>
</parent>

Answer 2

All pom implicitly inherit from superpom, which is present in the maven distribution. This pom contains default values ​​for all maven projects that can be overridden in your maven project. But most of these default values ​​are not overridden, since they usually form the conditional part of maven, since it is a building tool that focuses more on convention. For example, the assembly directory is the default target, and therefore this configuration is present in super pom as

........
<directory>${project.basedir}/target</directory>
.........

, ,