maven package with dependencies

Today encountered a Mavan warehouse does not have a jar package, it can only add local jar package, spent a lot of time to find information, finally OK. So this record.1. For the first time, see on the internet that can be solved with Dependencies> Dependency> groupId>XxxgroupId> Artifactid>XxxArtifactid> version>Xxxversion> Scope>SystemScope> Sys

dependent third-party jar, if the lookup classpath failed, will be error, you can first useMVN Dependency:copy-dependencies-doutputdirectory=target/libcommand to export all dependent jar packages to the Target/lib directory.Second, the use of Maven-jar-plugin modified meta-inf\manifest. MF manifest fileIn the final jar of Java application, with the Unzip tool open, you can see an important manifest file MA

When you publish your project, you may have the requirement that a jar package contains your own research code, as well as a dependent library (for example, after a log4j jar package), and there are two ways to do that when MAVEN packs. 1, using the Maven-assembly-plugin plugin The Pom.xml configuration is as follows

copy print? Then enter on the command line: MVN assembly:assembly You will find the newly generated {Artifactid}-jar-with-dependencies.jar file under the ${project}/target folder. In the execution of the above command, MAVEN exports the package that the jar package relies on, and extracts (unpackage) and puts it in the This {Artifactid}-jar-with-dependencies

> dependencies> -- dependency> groupId>org.springframework.bootgroupId> artifactid>spring-boot-starter-webartifactid> Dependency> dependency> groupId>org.springframework.bootgroupId> artifactid>spring-boot-starter-data-jpaartifactid> Dependency> -- dependency> groupId>mysqlgroupId> artifactid>mysql-connector-javaartifactid> Dependency> -- dependency> groupId>c

> dependencies> -- dependency> groupId>org.springframework.bootgroupId> artifactid>spring-boot-starter-webartifactid> Dependency> dependency> groupId>org.springframework.bootgroupId> artifactid>spring-boot-starter-data-jpaartifactid> Dependency> -- dependency> groupId>mysqlgroupId> artifactid>mysql-connector-javaartifactid> Dependency> -- dependency> groupId>c

> dependencies> -- dependency> groupId>org.springframework.bootgroupId> artifactid>spring-boot-starter-webartifactid> Dependency> dependency> groupId>org.springframework.bootgroupId> artifactid>spring-boot-starter-data-jpaartifactid> Dependency> -- dependency> groupId>mysqlgroupId> artifactid>mysql-connector-javaartifactid> Dependency> -- dependency> groupId>c

> dependencies> -- dependency> groupId>org.springframework.bootgroupId> artifactid>spring-boot-starter-webartifactid> Dependency> dependency> groupId>org.springframework.bootgroupId> artifactid>spring-boot-starter-data-jpaartifactid> Dependency> -- dependency> groupId>mysqlgroupId> artifactid>mysql-connector-javaartifactid> Dependency> -- dependency> groupId>c

Automatically download jar packages using Maven Right-click the project to convert the project into a MAVEN project Then go in Maven's official website http://mvnrepository.com/ There are a lot of jar packages for us to use, such as I'm now going to download a jsoup jar package Search Jsoup, click the first one Then there

Will rely on the break into the jar package, because Maven manages all the dependencies, so the project's code and dependencies into a package for it is a logical function. Maven This feature was used before, but this time forget

by us and does not need maven to go to the warehouse to find it. Specifying scope as system needs to be used with another property element, Systempath, which represents the location of the dependency on the current system, using an absolute path. For example, the website gives a tools.jar about using the JDK:Project> ... Dependencies> Dependency> groupId>Sun.jdkgroupId> Artifactid>ToolsArtif

In daily development we often need to package the project into a CLI (command line) package that can be run directly on the command lines. The default maven-generated jar package contains only the. class files and project resource files that were compiled, and a jar file that can be run directly from the command line t

Create a folder under any directory, under which you create a pom.xml file, a bat batch script; Select the bat batch script right-click Edit and copy the following: Call Mvn-f pom.xml dependency: Copy-dependencies@Pause Pom.xml does not need to be as complex as the actual project, the example is as follows (XML version= "1.0"?>Projectxmlns= "http://maven.apache.org/POM/4.0.0"Xmlns:xsi= "Http://www.w3.org/2001/XMLSchema-instance"xsi:schemalocation=

successfully download the associated jar packageSolution:Manually import the required jar packages yourselfHere's where Spark's jar bag is.The screenshot shows:Such as:All I need is Spark's relevant jar package.The configuration information added by the configuration file Pom.xml is as follows: Under MAVEN's library file, mine is .... \apache-maven-3.0.4\maven-depend