Maven hits the jar package and submits the private server

1.mvn clean package: package
2.mvn clean deploy: deploy and upload private server

If there is a problem with the corresponding test when packaging, you can skip it directly: -Dmaven.test.skip=true -Dmaven.javadoc.skip=true

When deploying There needs to be a corresponding private server address in the pom, including releases, snapshots
such as:
<distributionManagement>
    <repository>
        <id>iBlue-releases</id>
        <url>http://10.200.180.48:8081/nexus/content/repositories/ releases/</url>
    </repository>
    <snapshotRepository>
        <id>iBlue-snapshots</id>
        <url>http://10.200.180.48:8081/nexus/content/repositories/snapshots/</url>
    </ The problem with snapshotRepository>
</distributionManagement>

: if prompts such as can' when running cleanThe problem of t delete target is basically because the program is running locally, so the target cannot be cleared and needs to be closed.