This article is a mirror article of machine translation, please click here to jump to the original article.

Architect_Programmer_Code Agriculture Network»Architect › Programming › Java › The connection and difference between Maven commands package, install, and deploy...
View: 27770|Reply: 3

[Source] The connection and difference between the Maven commands package, install, and deploy

[Copy link]
Posted on 7/22/2021 11:08:55 AM | | |
mvn clean package executes seven stages in order: clean, resources, compile, testResources, testCompile, test, and jar (packaging).
mvn clean install performs eight stages in order: clean, resources, compile, testResources, testCompile, test, jar (package), and install.
mvn clean deploy executes nine stages in order: clean, resources, compile, testResources, testCompile, test, jar (package), install, and deploy.


package command completes project compilation, unit testing, and packaging functions, but does not deploy the executed JAR packages (war packages or other types of packages) to the local maven repository and the remote maven private server repository
install command completes the project compilation, unit testing, and packaging functions, and deploys the executable jar packages (war packages or other types of packages) to the local maven repository, but not to the remote maven private server repository
deploy command completes the project compilation, unit testing, and packaging functions, and deploys the executed JAR packages (war packages or other types of packages) to the local MAVEN repository and the remote MAVEN private server repository





Previous:The Linux history command shows the time and the executing user
Next:Linux kills a specified process by combining ps with kill

Related Posts
 Landlord| Posted on 12/17/2021 11:03:18 AM |
Push a third-party jar package to a local maven repository command:

 Landlord| Posted on 4/15/2024 9:37:25 AM |
Small slag Posted on 2021-12-17 11:03
Push a third-party jar package to a local maven repository command:

Maven Version Management:The hyperlink login is visible.


Other options

Maven version number specification
[Mandatory] Second-party library version number naming method: major version number. Subversion number. Revision number. Date suffix.
1) Major version number: The product direction changes, or large-scale APIs are incompatible, or the architecture is incompatible with upgrades.
2) Version number: Maintain relative compatibility, add major functional features, and the API with a very small impact is not compatible with modifications.
3) Revision number: Maintain full compatibility, fix bugs, add minor features, etc.
4) Date suffix: The application release date is always yyyyMMdd+ times (e.g., 1.0.2-2024041501)


 Landlord| Posted on 1/6/2025 4:47:13 PM |
Looking at the dependency tree:

Disclaimer:
All software, programming materials or articles published by Code Farmer Network are only for learning and research purposes; The above content shall not be used for commercial or illegal purposes, otherwise, users shall bear all consequences. The information on this site comes from the Internet, and copyright disputes have nothing to do with this site. You must completely delete the above content from your computer within 24 hours of downloading. If you like the program, please support genuine software, purchase registration, and get better genuine services. If there is any infringement, please contact us by email.
Mail To:help@itsvse.com