Example
1. Dependencies are as follows:
<dependency> <groupId>org.quartz-scheduler.internal</groupId> <artifactId> Quartz-terracotta-bootstrap</artifactid> <version>2.2.2-snapshot</version></ Dependency>
To install the jar package to the local Warehouse command:
MVN install:install-file-dfile=d:\quartz-terracotta-bootstrap-2.2.2-snapshot.jar-dgroupid= Org.quartz-scheduler.internal-dartifactid=quartz-terracotta-bootstrap-dversion=2.2.2-snapshot-dpackaging=jar
--DgroupId and DartifactId constitute the coordinates of the jar package in Pom.xml, corresponding to the dependentDgroupId and DartifactId
--Dfile indicates the absolute path of the jar package that needs to be uploaded
--Dpackaging for the type of installation file
2. Upload the jar to the
Command:
MVN deploy:deploy-file-dgroupid=org.terracotta.toolkit-dartifactid=terracotta-toolkit-api-internal-dversion= 1.12-dpackaging=jar-dfile=d:\terracotta-toolkit-api-internal-1.12.jar-durl=http://ip:port/nexus/content/ repositories/thirdparty/-drepositoryid=thirdparty
--DgroupId and DartifactId constitute the coordinates of the jar package in Pom.xml, corresponding to the dependentDgroupId and DartifactId
--Dfile indicates the absolute path of the jar package that needs to be uploaded
--The URL address of the warehouse on Durl (open the Nexus left repositories menu, you can see the path)
--The representation ID of the DrepositoryId server, which can be seen in the Nexus configuration
Maven: Install the jar to the local repository and the jar