maven package with dependencies

MAVEN's non-web projects need to refer to a lot of jar packages at execution time, which is usually done by unifying these jar packages into the Lib directory, and Maven's dependency plugin can do this for us.We need to add a plugin,plugin content within the plugins node of the build node of the Pom file as follows: PackagefalsefalsetruetrueIn the above configuration we used the Maven-dependency-plugin plug-in, and then performed the (execution node)

original configuration, for LIB reference this problem, only need to add is:Another popular science, maven directory contract:The directory where the Pom.xml is located should be the root of the project, assuming the directory is ${proj-dir}, then Maven has the following assumptions:${proj-dir}/src/main/java--. java files that store the project.${proj-dir}/src/main/resources--Store project resource files,

Date: 2016-7-15 content: How to add jar packages quickly and easily in Maven-furnished projects; Simple description: Recently in the three frameworks of Java learning, it is a cool tool to see some instructors using MAVEN to decorate and manage projects in the video. The use of the 666 is really not good. Then take the time to learn some of MAVEN's knowledge. But in building a

Introduction:Although MAVEN is configured to automatically download the jar package to the local Maven repository by indexing, this allows the project to use the rack package in the local warehouse directly,But this trick is not every time Turin should, also have encountered a failure, when encountered failure, we can

Nexus2 can upload jar packages to private libraries through the admin interface, but the newest NEXUS3 can't find the upload interface and can only be published to private libraries in the following ways.Publishing third-party jar packagesIn this case, the MAVEN remote repository does not have a local third-party jar package that needs to be published to the private library.mvn deploy:deploy-file -DgroupI

Typically, when using a MAVEN project, there are some local jar packages that need to be invested and relied upon, and can be implemented in the following ways1. Save the local jar package locally2. In the pom.xml of the project, I define the dependency information of the gruopid of the corresponding jar package.3. Enter the root directory of the local repository

Updating the jar package manually in Maven is a cumbersome task.Range dependencyThis step can be skipped. Some jar packages may be automatically upgradedBeatVersion! Official Instructions: dependency version ranges Range Meaning (, 1.0] Version ≤ 1.0 1.0 Fixed 1.0 version [1.0] [1.2, 1.3] 1.2 ≤ version ≤ 1.3 [1

When you use eclipse to package maven projects, the invalid LOC header (bad signature) exception is reported. eclipsemavenWhen packaging on eclipse, an error is returned: [INFO] Including org.codehaus.groovy:groovy-all:jar:2.4.3 in the shaded jar.[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ---------------------------------------------------------

Problem descriptionDependencies are configured in Pom.xml, but the dependency is not successful, or the dependency is not found in the local warehouse The approximate error is as follows:Artifactdescriptorexception:failed to read artifact descriptor for Commons-beanutils:commons-beanutils-core:jar : 1.8.0:artifactresolutionexception:could not transfer artifact commons-beanutils:commons-beanutils-core:pom:1.8.0Problem-solving ideas 1. Check to see if the local repository has this jar

Before using Eclipse to test MAVEN's Web project, you can automatically publish your workspace's Web project code to the F:\IWorkspace\.metadata\.plugins\ by clicking "Clean" on the inside of the Eclipse Tomcat right button. Org.eclipse.wst.server.core\tmp2\wtpwebapps "This path is very convenient. If the war package deployed in Tomcat chooses the "Add External Web Module", then the test is going to cry. The MAVEN