I've read the section in the Maven documentation, but I haven't really seen any evidence of plugins using the <ciManagement>
tag in a project POM.
My question is:
"Maven" is really just a core framework for a collection of Maven Plugins. In other words, plugins are where much of the real action is performed, plugins are used to: create jar files, create war files, compile code, unit test code, create project documentation, and on and on.
project. basedir : The directory that the current project resides in. This means this points to where your Maven projects resides on your system. It corresponds to the location of the pom. xml file.
pluginManagement: is an element that is seen along side plugins. Plugin Management contains plugin elements in much the same way, except that rather than configuring plugin information for this particular project build, it is intended to configure project builds that inherit from this one.
A Project Object Model or POM is the fundamental unit of work in Maven. It is an XML file that contains information about the project and configuration details used by Maven to build the project.
for documentation sample http://maven.apache.org/plugins/maven-compiler-plugin/integration.html
Historically this element was used by continuum for more details see http://maven.apache.org/ref/3.0.4/maven-model/maven.html#class_ciManagement it was possible to define the pom notifiers (mail,irc) and where to send notification.
SonarQube uses the <ciManagement>
element of the pom to define the value of its own sonar.links.ci
configuration property. This property is mentioned in the SonarQube documentation, but there's no explanation about what is it used for. It turns out it's one more thing to keep up-to-date. I would try to remove it from the pom to see if any visible issue comes up.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With