Maven project's Common module Jar is uploaded to the repository and is dependent on other modules

1both the parent Pom and the common Pom need to be added<Distributionmanagement>    <Repository>        <Id>Nexus</Id>        <Name>Nexus ThirdParty repositories</Name>        <Url>http//10.74.11.37:8081/Nexus/Content/Repositories/ThirdParty</wr.>    </Repository></Distributionmanagement>where the ID is to be associated with the MAVEN configuration file settings.xml inside the<Server>    <Id>Nexus-Releases</Id>    <Username>Admin</Username>    <Password>Mtait</Password></Server><Server>    <Id>Nexus-Snapshots</Id>    <Username>Admin</Username>    <Password>Mtait</Password></Server><Server>    <Id>Nexus</Id>    <Username>Admin</Username>    <Password>Mtait</Password></Server><Server>    <Id>Tomcat.server</Id>    <Username>Mtait</Username>    <Password>Mtait</Password></Server></Servers>The ID remains the same;2. Common jar automatically uploads to Maven repository, right-common project, run as--"build...--" goals filled in deploy--"run, will be automatically uploaded to the Maven warehouseHowever, there is a premise in the private library, click Repository, select the path to store the jar--"configuration--" Access settings--"Deployment policy--" select Allow Redeploy3. Parent Pom inside<Dependency>    <GroupId>Com.mintaian.riskcontrol</GroupId>    <Artifactid>Riskcontrol-Common</Artifactid>    <Version>1.0.0</Version></Dependency>Other Modules Pom<Dependency>    <GroupId>Com.mintaian.riskcontrol</GroupId>    <Artifactid>Riskcontrol-Common</Artifactid></Dependency>4Dependencies may not introduce a jar but a local project, the workaround: Right-click the project--"maven--" selects the Enable Workspace Resolution, which is the introduction of the jar

Maven project's Common module Jar is uploaded to the repository and is dependent on other modules