当前位置：网站首页>pom. Brief introduction of XML configuration file label function
pom. Brief introduction of XML configuration file label function
2022-07-07 20:00:00 【Whiteye too white】
pom.xml Brief description of the role of profile labels
<!-- Project configuration -->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0http://maven.apache.org/maven-v4_0_0.xsd">
<!-- Coordinates of the parent project . If the value of an element is not specified in the project , Then the corresponding value in the parent project is the default value of the project . The coordinates include group ID,artifact ID and version.-->
<parent>
<!-- The component identifier of the inherited parent project -->
<artifactId><artifactId/>
<!-- The globally unique identifier of the inherited parent project -->
<groupId><groupId/>
<!-- The version of the inherited parent project -->
<version><version/>
<!-- The purpose of the parent pom.xml The relative path of the file . Relative paths allow you to choose a different path . The default value is ../pom.xml.Maven First, look for the parent where the current project is built Purpose pom, Next, in this location of the file system （relativePath Location ）, And then in the local warehouse , Finally, find the parent project in the remote warehouse pom.-->
<relativePath><relativePath/>
</parent>
<!-- Declare which... The project descriptor follows POM Model version . The version of the model itself rarely changes , Even so , But it's still essential , This is to be Maven When new features or other model changes are introduced , Ensure stability .-->
<modelVersion>4.0.0</modelVersion>
<!-- The globally unique identifier of the project , A fully qualified package name is usually used to distinguish this project from other projects . And the path generated at build time is also generated from this , Such as com.mycompany.app The relative path generated is ：/com/mycompany/app-->
<groupId>asia.banseon</groupId>
<!-- Identifier of the component , It and group ID Identify a component together . let me put it another way , You can't have two different projects with the same artifact ID and groupID; In a certain specific group ID Next ,artifact ID It has to be unique . A component is something that a project produces or uses ,Maven The artifacts generated for the project include ：JARs, Source code , Binary publishing and WARs etc. .-->
<artifactId>banseon-maven2</artifactId>
<!-- The types of components produced by the project , for example jar、war、ear、pom. Plugins can create their own component types , So not all of the component types listed above -->
<packaging>jar</packaging>
<!-- The current version of the project , The format is : Main version . Next version . Incremental version - Limited version number -->
<version>1.0-SNAPSHOT</version>
<!-- Name of the project , Maven The generated document uses -->
<name>banseon-maven</name>
<!-- Project home page URL, Maven The generated document uses -->
<url>http://www.baidu.com/banseon</url>
<!-- A detailed description of the project , Maven The generated document uses . When this element can be used HTML Format description （ for example ,CDATA The text in will be ignored by the parser , You can include HTML mark sign ）, The use of plain text to describe . If you need to modify the resulting web Index page of the site , You should modify your own index page file , Instead of adjusting the documents here .-->
<description>A maven project to study maven.</description>
<!-- Describes the prerequisites for the project build environment .-->
<prerequisites>
<!-- What you need to build the project or use the plug-in Maven The minimum version of -->
<maven/>
</prerequisites>
<!-- Project problem management system (Bugzilla, Jira, Scarab, Or any problem management system you like ) Name and URL, For this example jira-->
<issueManagement>
<!-- Problem management system （ for example jira） Name ,-->
<system>jira</system>
<!-- The project uses the problem management system of URL-->
<url>http://jira.baidu.com/banseon</url>
</issueManagement>
<!-- Project continuously integrates information -->
<ciManagement>
<!-- The name of the continuous integration system , for example continuum-->
<system/>
<!-- The project uses a continuous integration system of URL（ If the continuous integration system has web Interface ）.-->
<url/>
<!-- When the build is complete , Developers who need to be notified / User's configuration items . Including the information of the informed and the notice conditions （ error , Failure , success , Warning ）-->
<notifiers>
<!-- Configure a way , When the build breaks , Notify the user in this way / developer -->
<notifier>
<!-- The way to send the notice -->
<type/>
<!-- Whether to notify when an error occurs -->
<sendOnError/>
<!-- Whether to notify when the build fails -->
<sendOnFailure/>
<!-- Whether to notify when the build is successful -->
<sendOnSuccess/>
<!-- Whether to notify when a warning occurs -->
<sendOnWarning/>
<!-- Disfavor use . Where to send the notice -->
<address/>
<!-- Extended configuration items -->
<configuration/>
</notifier>
</notifiers>
</ciManagement>
<!-- The year the project was created ,4 Digit number . Use this value when generating copyright information .-->
<inceptionYear/>
<!-- Project related mailing list information -->
<mailingLists>
<!-- This element describes all mailing lists related to the project . Automatically generated sites reference this information .-->
<mailingList>
<!-- The name of the email -->
<name>Demo</name>
<!-- Address or link to send mail , If it's an email address , When creating a document ,mailto: Links will be created automatically -->
<post>[email protected]</post>
<!-- The address or link to which you subscribe , If it's an email address , When creating a document ,mailto: Links will be created automatically -->
<subscribe>[email protected]</subscribe>
<!-- Unsubscribe from email address or link , If it's an email address , When creating a document ,mailto: Links will be created automatically -->
<unsubscribe>[email protected]</unsubscribe>
<!-- You can browse email messages URL-->
<archive>http:/hi.baidu.com/banseon/demo/dev/</archive>
</mailingList>
</mailingLists>
<!-- Project developer list -->
<developers>
<!-- Information of a project developer -->
<developer>
<!--SCM The unique identifier of the project developer -->
<id>HELLO WORLD</id>
<!-- The full name of the project developer -->
<name>banseon</name>
<!-- Project developer's email-->
<email>[email protected]</email>
<!-- Project developer's home page URL-->
<url/>
<!-- The role of the project developer in the project , The role element describes the various roles -->
<roles>
<role>Project Manager</role>
<role>Architect</role>
</roles>
<!-- Project developer's organization -->
<organization>demo</organization>
<!-- Of the project developer's organization URL-->
<organizationUrl>http://hi.baidu.com/banseon</organizationUrl>
<!-- Project developer properties , How to deal with instant messages, etc -->
<properties>
<dept>No</dept>
</properties>
<!-- Project developer's time zone , -11 To 12 Range of integers .-->
<timezone>-5</timezone>
</developer>
</developers>
<!-- List of other contributors to the project -->
<contributors>
<!-- Other contributors to the project . See developers/developer Elements -->
<contributor>
<name/><email/><url/><organization/><organizationUrl/><roles/><timezone/><properties/>
</contributor>
</contributors>
<!-- This element describes all of the License list . Only the license list , Don't list dependent projects license list . If more than one is listed license, Users can choose one of them instead of accepting all license.-->
<licenses>
<!-- Describes the license, For building projects web Site license page , Some other reports and validation This element is also used .-->
<license>
<!--license A legal name -->
<name>Apache 2</name>
<!-- Official license Of the body page URL-->
<url>http://www.baidu.com/banseon/LICENSE-2.0.txt</url>
<!-- The main way of project distribution ： repo, It can be downloaded from Maven Library Download manual, Users must download and install dependencies manually -->
<distribution>repo</distribution>
<!-- About license Additional information -->
<comments>A business-friendly OSS license</comments>
</license>
</licenses>
<!--SCM(Source Control Management) Tags allow you to configure your code base , for Maven web Site and other plug-ins use .-->
<scm>
<!--SCM Of URL, The URL Describes the version library and how to connect to it . For details , Please have a look at SCMs Provided URL Format and list . The connection is read-only .-->
<connection>
scm:svn:http://svn.baidu.com/banseon/maven/banseon/banseon-maven2-trunk(dao-trunk)
</connection>
<!-- For developers , similar connection Elements . That is, the connection is not only read-only -->
<developerConnection>
scm:svn:http://svn.baidu.com/banseon/maven/banseon/dao-trunk
</developerConnection>
<!-- The label of the current code , It defaults to HEAD-->
<tag/>
<!-- Point to the browsable... Of the project SCM library （ for example ViewVC perhaps Fisheye） Of URL.-->
<url>http://svn.baidu.com/banseon</url>
</scm>
<!-- Describe the various attributes of the organization to which the project belongs .Maven The generated document uses -->
<organization>
<!-- The full name of the organization -->
<name>demo</name>
<!-- Organize home page URL-->
<url>http://www.baidu.com/banseon</url>
</organization>
<!-- The information needed to build the project -->
<build>
<!-- This element sets the source directory of the project , When building a project , Build the system to compile the source code in the directory . The path is relative to pom.xml Relative path of .-->
<sourceDirectory/>
<!-- This element sets the source directory of the project script , This directory is different from the source directory ： In most cases , The contents of this directory Will be copied to the output directory ( Because the script is interpreted , Instead of being compiled ).-->
<scriptSourceDirectory/>
<!-- This element sets the source directory used by the project unit test , When testing a project , Build the system to compile the source code in the directory . The path is relative to pom.xml Relative path of .-->
<testSourceDirectory/>
<!-- Compiled applications class The directory where the files are stored .-->
<outputDirectory/>
<!-- Compiled tests class The directory where the files are stored .-->
<testOutputDirectory/>
<!-- Use a series of build extensions from the project -->
<extensions>
<!-- Describe the build extensions used .-->
<extension>
<!-- Build extended groupId-->
<groupId/>
<!-- Build extended artifactId-->
<artifactId/>
<!-- Build the extended version -->
<version/>
</extension>
</extensions>
<!-- When the project doesn't set goals （Maven2 It's called stage ） The default value of -->
<defaultGoal/>
<!-- This element describes a list of all resource paths associated with the project , For example, property files related to projects , These resources are included in the final packaging file .-->
<resources>
<!-- This element describes all the resource paths associated with a project or test -->
<resource>
<!-- Describes the target path of the resource . This path is relative to target/classes Catalog （ for example ${project.build.outputDirectory}）. For example Son , If you want resources in a specific package (org.apache.maven.messages), You have to set this element to org/apache/maven /messages. However , If you just want to put resources in the source directory structure , You don't need to configure .-->
<targetPath/>
<!-- Use parameter value instead of parameter name . The parameter value is taken from properties Elements or attributes configured in files , The file in filters Elements .-->
<filtering/>
<!-- Describe the directory where the resources are stored , This path is relative to POM route -->
<directory/>
<!-- List of included patterns , for example **/*.xml.-->
<includes/>
<!-- List of excluded modes , for example **/*.xml-->
<excludes/>
</resource>
</resources>
<!-- This element describes all the resource paths associated with unit testing , For example, property files related to unit tests .-->
<testResources>
<!-- This element describes all the resource paths associated with the test , See build/resources/resource Description of the elements -->
<testResource>
<targetPath/><filtering/><directory/><includes/><excludes/>
</testResource>
</testResources>
<!-- Build the directory where all the generated files are stored -->
<directory/>
<!-- The filename of the generated component , The default value is ${artifactId}-${version}.-->
<finalName/>
<!-- When filtering When the switch is on , List of filter properties files used -->
<filters/>
<!-- Default plug-in information that subprojects can reference . The plug-in configuration item will not be resolved or bound to the lifecycle until it is referenced . Any local configuration of a given plug-in will override the configuration here -->
<pluginManagement>
<!-- List of plug-ins used .-->
<plugins>
<!--plugin The element contains the information needed to describe the plug-in .-->
<plugin>
<!-- The plug-in is in the warehouse group ID-->
<groupId/>
<!-- The plug-in is in the warehouse artifact ID-->
<artifactId/>
<!-- The version of the plug-in being used （ Or version range ）-->
<version/>
<!-- Whether to download from the plug-in Maven Expand （ For example, packaging and type processor ）, Due to performance , Only when you really need to download , This element is set to enabled.-->
<extensions/>
<!-- Perform the configuration of a set of goals in the build lifecycle . Each target may have a different configuration .-->
<executions>
<!--execution Element contains the information needed for plug-in execution -->
<execution>
<!-- Identifier of the execution target , Used to identify goals in the build process , Or match the execution targets that need to be merged in the inheritance process -->
<id/>
<!-- The build lifecycle phase that binds the target , If omitted , The target will be bound to the default phase of the configuration in the source data -->
<phase/>
<!-- The execution target of the configuration -->
<goals/>
<!-- Whether the configuration is propagated to child POM-->
<inherited/>
<!-- As DOM Object configuration -->
<configuration/>
</execution>
</executions>
<!-- Additional dependencies required for the project to introduce plug-ins -->
<dependencies>
<!-- See dependencies/dependency Elements -->
<dependency>
......
</dependency>
</dependencies>
<!-- Whether any configuration is propagated to subprojects -->
<inherited/>
<!-- As DOM Object configuration -->
<configuration/>
</plugin>
</plugins>
</pluginManagement>
<!-- List of plug-ins used -->
<plugins>
<!-- See build/pluginManagement/plugins/plugin Elements -->
<plugin>
<groupId/><artifactId/><version/><extensions/>
<executions>
<execution>
<id/><phase/><goals/><inherited/><configuration/>
</execution>
</executions>
<dependencies>
<!-- See dependencies/dependency Elements -->
<dependency>
......
</dependency>
</dependencies>
<goals/><inherited/><configuration/>
</plugin>
</plugins>
</build>
<!-- Build projects in the column profile, If activated , The build processing will be modified -->
<profiles>
<!-- Activate a build process based on environment or command line parameters -->
<profile>
<!-- Unique identifier of the build configuration . It is used for command line activation , Also used to merge... With the same identifier on inheritance profile.-->
<id/>
<!-- Automatic triggering profile The conditional logic of .Activation yes profile The key to the door .profile Power comes from it The ability to automatically use certain values in certain environments ; These environments pass through activation Element designation .activation The element is not activated profile The only way .-->
<activation>
<!--profile The default activation flag -->
<activeByDefault/>
<!-- When it matches jdk Detected ,profile To be activated . for example ,1.4 Activate JDK1.4,1.4.0_2, and !1.4 Activating all versions is not to 1.4 At the beginning JDK.-->
<jdk/>
<!-- When a matching operating system property is detected ,profile To be activated .os Element can define some operating system related properties .-->
<os>
<!-- Activate profile The name of the operating system -->
<name>Windows XP</name>
<!-- Activate profile The operating system family of ( Such as 'windows')-->
<family>Windows</family>
<!-- Activate profile The operating system architecture of -->
<arch>x86</arch>
<!-- Activate profile The operating system version of -->
<version>5.1.2600</version>
</os>
<!-- If Maven An attribute was detected （ Its value can be in POM Pass through ${ name } quote ）, It has the corresponding name and value ,Profile Will be activated . If value The field is empty , Then the existence of the attribute name field will activate profile, Otherwise, match the property value fields in case sensitive way -->
<property>
<!-- Activate profile The name of the property of -->
<name>mavenVersion</name>
<!-- Activate profile The value of the property -->
<value>2.0.3</value>
</property>
<!-- Provide a filename , Activate... By detecting whether the file exists or does not exist profile.missing Check if the file exists , Activate if not present profile. On the other hand ,exists It will check if the file exists , Activate... If present profile.-->
<file>
<!-- If the specified file exists , Then activate profile.-->
<exists>/usr/local/hudson/hudson-home/jobs/maven-guide-zh-to-production/workspace/</exists>
<!-- If the specified file does not exist , Then activate profile.-->
<missing>/usr/local/hudson/hudson-home/jobs/maven-guide-zh-to-production/workspace/</missing>
</file>
</activation>
<!-- The information needed to build the project . See build Elements -->
<build>
<defaultGoal/>
<resources>
<resource>
<targetPath/><filtering/><directory/><includes/><excludes/>
</resource>
</resources>
<testResources>
<testResource>
<targetPath/><filtering/><directory/><includes/><excludes/>
</testResource>
</testResources>
<directory/><finalName/><filters/>
<pluginManagement>
<plugins>
<!-- See build/pluginManagement/plugins/plugin Elements -->
<plugin>
<groupId/><artifactId/><version/><extensions/>
<executions>
<execution>
<id/><phase/><goals/><inherited/><configuration/>
</execution>
</executions>
<dependencies>
<!-- See dependencies/dependency Elements -->
<dependency>
......
</dependency>
</dependencies>
<goals/><inherited/><configuration/>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<!-- See build/pluginManagement/plugins/plugin Elements -->
<plugin>
<groupId/><artifactId/><version/><extensions/>
<executions>
<execution>
<id/><phase/><goals/><inherited/><configuration/>
</execution>
</executions>
<dependencies>
<!-- See dependencies/dependency Elements -->
<dependency>
......
</dependency>
</dependencies>
<goals/><inherited/><configuration/>
</plugin>
</plugins>
</build>
<!-- modular （ Sometimes called subprojects ） Be built as part of the project . Each module element listed is a relative path to the directory of the module -->
<modules/>
<!-- Discover the list of dependent and extended remote repositories .-->
<repositories>
<!-- See repositories/repository Elements -->
<repository>
<releases>
<enabled/><updatePolicy/><checksumPolicy/>
</releases>
<snapshots>
<enabled/><updatePolicy/><checksumPolicy/>
</snapshots>
<id/><name/><url/><layout/>
</repository>
</repositories>
<!-- List of remote repositories where plug-ins are found , These plug-ins are used for building and reporting -->
<pluginRepositories>
<!-- Contains the information needed to connect to the remote plug-in Repository . See repositories/repository Elements -->
<pluginRepository>
<releases>
<enabled/><updatePolicy/><checksumPolicy/>
</releases>
<snapshots>
<enabled/><updatePolicy/><checksumPolicy/>
</snapshots>
<id/><name/><url/><layout/>
</pluginRepository>
</pluginRepositories>
<!-- This element describes all the dependencies associated with the project . These dependencies make up every part of the project construction process . They are automatically downloaded from the project defined Repository . For more information , See project dependency mechanism .-->
<dependencies>
<!-- See dependencies/dependency Elements -->
<dependency>
......
</dependency>
</dependencies>
<!-- Disfavor use . Now? Maven Ignore this element .-->
<reports/>
<!-- This element includes the specification for using report plug-ins to generate reports . When the user executes “mvn site”, These reports will run . You can see the links of all reports in the page navigation bar . See reporting Elements -->
<reporting>
......
</reporting>
<!-- See dependencyManagement Elements -->
<dependencyManagement>
<dependencies>
<!-- See dependencies/dependency Elements -->
<dependency>
......
</dependency>
</dependencies>
</dependencyManagement>
<!-- See distributionManagement Elements -->
<distributionManagement>
......
</distributionManagement>
<!-- See properties Elements -->
<properties/>
</profile>
</profiles>
<!-- modular （ Sometimes called subprojects ） Be built as part of the project . Each module element listed is a relative path to the directory of the module -->
<modules/>
<!-- Discover the list of dependent and extended remote repositories .-->
<repositories>
<!-- Contains information that needs to be connected to the remote warehouse -->
<repository>
<!-- How to deal with the download of the released version in the remote warehouse -->
<releases>
<!--true perhaps false Indicates whether the repository is downloading a certain type of component （ Release , Snapshot version ） Turn on . -->
<enabled/>
<!-- This element specifies how often updates occur .Maven It's more local POM And remote POM The timestamp . The option here is ：always（ always ）,daily（ Default , everyday ）,interval：X（ here X It's a time interval in minutes ）, perhaps never（ never ）.-->
<updatePolicy/>
<!-- When Maven What to do when verifying component validation file fails ：ignore（ Ignore ）,fail（ Failure ）, perhaps warn（ Warning ）.-->
<checksumPolicy/>
</releases>
<!-- How to handle the download of snapshot version in remote warehouse . With releases and snapshots These two sets of configurations ,POM It can be in every single warehouse , Take a different... For each type of component Strategy . for example , Someone may decide to turn on support for snapshot version download for development purposes only . See repositories/repository/releases Elements -->
<snapshots>
<enabled/><updatePolicy/><checksumPolicy/>
</snapshots>
<!-- Remote warehouse unique identifier . Can be used to match in settings.xml Remote warehouse configured in the file -->
<id>banseon-repository-proxy</id>
<!-- Remote warehouse name -->
<name>banseon-repository-proxy</name>
<!-- Remote warehouse URL, Press protocol://hostname/path form -->
<url>http://192.168.1.169:9999/repository/</url>
<!-- Type of warehouse layout used to locate and sort components - It can be default（ Default ） perhaps legacy（ Legacy ）.Maven 2 Provides a default layout for its warehouse ; however and ,Maven 1.x There is a different layout . We can use this element to specify that the layout is default（ Default ） still legacy（ Legacy ）.-->
<layout>default</layout>
</repository>
</repositories>
<!-- List of remote repositories where plug-ins are found , These plug-ins are used for building and reporting -->
<pluginRepositories>
<!-- Contains the information needed to connect to the remote plug-in Repository . See repositories/repository Elements -->
<pluginRepository>
......
</pluginRepository>
</pluginRepositories>
<!-- This element describes all the dependencies associated with the project . These dependencies make up every part of the project construction process . They are automatically downloaded from the project defined Repository . For more information , See project dependency mechanism .-->
<dependencies>
<dependency>
<!-- Rely on the group ID-->
<groupId>org.apache.maven</groupId>
<!-- Rely on the artifact ID-->
<artifactId>maven-artifact</artifactId>
<!-- Dependent version number . stay Maven 2 in , It can also be configured as the range of version number .-->
<version>3.8.1</version>
<!-- Dependency type , The default type is jar. It usually represents the extension of the dependent file , But there are exceptions . A type can be mapped to another extension or classifier . The type often corresponds to the packaging used , Although there are exceptions . Some types of examples ：jar,war,ejb-client and test-jar. If you set extensions by true, You can go to plugin To define a new type . So the previous examples of types are incomplete .-->
<type>jar</type>
<!-- Dependent classifiers . The classifier can distinguish the same POM, But the components of different ways of building . The classifier name is appended to the version number of the filename . for example , If you want to build two separate components into JAR, A use Java 1.4 compiler , Another use Java 6 compiler , You can use a classifier to generate two separate JAR artifacts .-->
<classifier></classifier>
<!-- Depend on the range . In the process of project release , Help decide which components are included . For details, please refer to dependency mechanism . - compile ： Default range , Used to compile - provided： Similar to compiling , But support your expectations jdk Or the container provides , Be similar to classpath - runtime: You need to use - test: be used for test Use - system: Need to provide corresponding elements externally . adopt systemPath To obtain - systemPath: Only used in the range of system. Provide the appropriate path - optional: When the project itself is dependent , Mark whether the dependency passes . Used for continuous dependency -->
<scope>test</scope>
<!-- Only for system Scope use . Be careful , The use of this element... Is discouraged , And in the new version the element may be overridden . This element specifies the path on the file system for dependencies . You need an absolute path instead of a relative path . It is recommended to match the absolute path with the attribute , for example ${java.home}.-->
<systemPath></systemPath>
<!-- When calculating transitive dependencies , From the list of dependent components , List excluded dependent component sets . That is to say maven You only depend on the specified project , Don't rely on project dependencies . This element is mainly used to solve version conflicts -->
<exclusions>
<exclusion>
<artifactId>spring-core</artifactId>
<groupId>org.springframework</groupId>
</exclusion>
</exclusions>
<!-- Optional dependency , If you're on a project B Zhongba C Dependency declaration is optional , You need to rely on B Project （ For example, project A） An explicit reference to C Dependence . Optional dependency blocks the transitivity of dependency .-->
<optional>true</optional>
</dependency>
</dependencies>
<!-- Disfavor use . Now? Maven Ignore this element .-->
<reports></reports>
<!-- This element describes the specification of using report plug-ins to generate reports . When the user executes “mvn site”, These reports will run . You can see the links of all reports in the page navigation bar .-->
<reporting>
<!--true, be , The site does not include default reports . This includes “ Project information ” Report in menu .-->
<excludeDefaults/>
<!-- Where to store all generated reports . The default value is ${project.build.directory}/site.-->
<outputDirectory/>
<!-- Report plugins used and their configuration .-->
<plugins>
<!--plugin Element contains the information needed to describe the report plug-in -->
<plugin>
<!-- The report plug-in is in the warehouse group ID-->
<groupId/>
<!-- The report plug-in is in the warehouse artifact ID-->
<artifactId/>
<!-- The version of the report plug-in used （ Or version range ）-->
<version/>
<!-- Whether any configuration is propagated to subprojects -->
<inherited/>
<!-- Configuration of report plug-in -->
<configuration/>
<!-- Multiple specifications for a set of reports , Each specification may have a different configuration . A norm （ Report set ） Corresponding to an implementation target . for example , Yes 1,2,3,4,5,6,7,8,9 Reports .1,2,5 constitute A Report set , Corresponding to an implementation target .2,5,8 constitute B Report set , Corresponding to another execution target -->
<reportSets>
<!-- Represents a collection of reports , And the configuration that generated the collection -->
<reportSet>
<!-- Unique identifier of the report collection ,POM Inheritance uses -->
<id/>
<!-- When generating a report collection , Configuration of used reports -->
<configuration/>
<!-- Whether the configuration is inherited to the child POMs-->
<inherited/>
<!-- Which reports are used in this collection -->
<reports/>
</reportSet>
</reportSets>
</plugin>
</plugins>
</reporting>
<!-- Default dependency information inherited from all subprojects of the project . This part of the dependency information will not be parsed immediately , But when the subproject declares a dependency （ Must describe group ID and artifact ID Information ）, If group ID and artifact ID Other information is not described , Through group ID and artifact ID Match the dependency here , And use the dependency information here .-->
<dependencyManagement>
<dependencies>
<!-- See dependencies/dependency Elements -->
<dependency>
......
</dependency>
</dependencies>
</dependencyManagement>
<!-- Project distribution information , In execution mvn deploy Post indicates the location to be published . With this information, you can deploy the website to a remote server or the components to a remote warehouse .-->
<distributionManagement>
<!-- Information needed to deploy project generated artifacts to remote repositories -->
<repository>
<!-- Is a unique version number assigned to the snapshot （ By timestamp and build serial number ）？ Still use the same version number every time ？ See repositories/repository Elements -->
<uniqueVersion/>
<id>banseon-maven2</id>
<name>banseon maven2</name>
<url>file://${basedir}/target/deploy</url>
<layout/>
</repository>
<!-- Where to deploy the snapshot of the component ？ If the element is not configured , Default deployment to repository Warehouse for element configuration , See distributionManagement/repository Elements -->
<snapshotRepository>
<uniqueVersion/>
<id>banseon-maven2</id>
<name>Banseon-maven2 Snapshot Repository</name>
<url>scp://svn.baidu.com/banseon:/usr/local/maven-snapshot</url>
<layout/>
</snapshotRepository>
<!-- Information needed to deploy the project's website -->
<site>
<!-- Unique identifier of the deployment location , To match the site with settings.xml Configuration in file -->
<id>banseon-site</id>
<!-- The name of the deployment location -->
<name>business api website</name>
<!-- Deployment location URL, Press protocol://hostname/path form -->
<url>
scp://svn.baidu.com/banseon:/var/www/localhost/banseon-web
</url>
</site>
<!-- Project download page URL. If there is no such element , Users should refer to the home page . The reason for using this element is ： Help locate components that are not in the warehouse （ because license Limit ）.-->
<downloadUrl/>
<!-- If the component has a new group ID and artifact ID（ The component moved to a new location ）, Here is the relocation information of the component .-->
<relocation>
<!-- The component is new group ID-->
<groupId/>
<!-- The component is new artifact ID-->
<artifactId/>
<!-- New version number of component -->
<version/>
<!-- Displayed to the user , Additional information about mobile , For example, the reason .-->
<message/>
</relocation>
<!-- Give the status of the component in the remote warehouse . This element must not be set in the local project , Because it's automatically updated by the tool . The valid values are ：none（ Default ）,converted（ Warehouse keeper from Maven 1 POM Switch over ）,partner（ Directly from a partner Maven 2 The warehouse is synchronized ）,deployed（ from Maven 2 Example Department office ）,verified（ Correct and final when verified ）.-->
<status/>
</distributionManagement>
<!-- Replace the name with a value ,Properties Can be in the whole POM Use in , It can also be used as a trigger （ see settings.xml In the configuration file activation Description of the elements ）. The format is <name>value</name>.-->
<properties/>
</project>
边栏推荐
- Flink并行度和Slot详解
- [RT thread env tool installation]
- what‘s the meaning of inference
- Leetcode force buckle (Sword finger offer 36-39) 36 Binary search tree and bidirectional linked list 37 Serialize binary tree 38 Arrangement of strings 39 Numbers that appear more than half of the tim
- What does "true" mean
- pom.xml 配置文件标签作用简述
- vulnhub之school 1
- Automatic classification of defective photovoltaic module cells in electroluminescence images-论文阅读笔记
- 831. KMP string
- LeetCode 648（C＃）
猜你喜欢
LeetCode_ 7_ five
vulnhub之Funfox2
PMP practice once a day | don't get lost in the exam -7.7
Kirin Xin'an with heterogeneous integration cloud financial information and innovation solutions appeared at the 15th Hunan Financial Technology Exchange Conference
Ways to improve the utilization of openeuler resources 01: Introduction
Redis——基本使用（key、String、List、Set 、Zset 、Hash、Geo、Bitmap、Hyperloglog、事务 ）
Is PMP beneficial to work? How to choose a reliable platform to make it easier to prepare for the exam!!!
关于ssh登录时卡顿30s左右的问题调试处理
RESTAPI 版本控制策略【eolink 翻译】
【STL】vector
随机推荐
Simulate the implementation of string class
UCloud是基础云计算服务提供商
A pot of stew, a collection of common commands of NPM and yarn cnpm
Automatic classification of defective photovoltaic module cells in electroluminescence images-論文閱讀筆記
R language ggplot2 visualization: use the ggviolin function of ggpubr package to visualize the violin diagram, set the palette parameter to customize the filling color of violin diagrams at different
Install mysql8 for Linux X ultra detailed graphic tutorial
mysql 的一些重要知识
Compiler optimization (4): inductive variables
R语言ggplot2可视化：使用ggpubr包的ggqqplot函数可视化QQ图（Quantile-Quantile plot）
Notes...
Training IX basic configuration of network services
九章云极DataCanvas公司摘获「第五届数字金融创新大赛」最高荣誉！
R language dplyr package mutate_ At function and min_ The rank function calculates the sorting sequence number value and ranking value of the specified data column in the dataframe, and assigns the ra
Chapter 9 Yunji datacanvas was rated as 36 krypton "the hard core technology enterprise most concerned by investors"
R language ggplot2 visualization: use the ggecdf function of ggpubr package to visualize the grouping experience cumulative density distribution function curve, and the linetype parameter to specify t
Sword finger offer II 013 Sum of two-dimensional submatrix
Ways to improve the utilization of openeuler resources 01: Introduction
“本真”是什么意思
爬虫实战（七）：爬王者英雄图片
8 CAS