MAVEN is a project management tool, and if we don't tell it what version of the JDK our code is going to compile with, it will be processed with the default JDK version of Maven-compiler-plugin, which makes it prone to version mismatches. Problems that could lead to a compilation that does not pass. For example, if a new feature of jdk1.7 is used in the code, but
MAVEN is essentially a framework for executing plug-ins. Plug-ins are divided into two categories: Build plug-ins and reporting plugins.
The build plugin , which is executed during the build phase, should be configured in the
Reporting plug-ins , which are executed when the site is generated, should be configured in the
But all plugins need to specify at least: GroupId, Artifactid, and
One: Maven official1, https://maven.apache.org/download.cgi2. Unzip the directory structure as followsTwo: Add MAVEN environment variables1. Add Maven_home2, add maven_home under PathThird, test whether the installation is successful1, enter mvn-version at the command line, the following prompt indicates successIv. myeclipse Add maven Plugin1. Select the preferen
localrepository > E:\Repositories\Mavenlocalrepository>6. Run CMD window, enter mvn help:system downloadEclipse plug-in installation:There are two kinds of installation methods, one is an online installation and one is an off-line installation.Online: Installation Address (HTTP://M2ECLIPSE.SONATYPE.ORG/SITES/M2E)Offline:1. Create a link and myplugins two folders in the Eclipse directory2. Download the eclipse-maven3-plugin.7z and compress it into th
By default, the Maven test/maven package/maven Install command generates output information in TXT and XML format in the Target/surefire-reports directory.In fact, Maven can also generate a report in HTML format, just need to use a plugin:
An error in Eclipse's tip in its pom file is as follows:Plugin execution not covered by lifecycle Configuration:org.apache.maven.plugins:maven-compiler-plugin:3.1:compile ( Execution:default-compile, Phase:compile)This means that M2E does not define the plug-in when it executes the MAVEN lifecycle management, so there is a hint of an error, in fact M2E provides an extension mechanism, and we can eliminate t
I use the community version of Idea, the community version of the No Tomcat plugin, only use the Maven plugin for Tomcat use, the following to get to the pointI. Pom.xml Configuring the Tomcat PluginBuild> Finalname>JavademoFinalname> Plugins> plugin> groupId>Org.apache.tomcat.mavengroupId> Art
Idea is packaged in three ways:
1, through the idea of the function of a step-by-step construction, more cumbersome;
2, through the Maven-shade-plugin plug-in packaging;
2, through the Maven-assembly-plugin plug-in packaging;
Here's the simplest way to do this: package with the Mav
1. Download maven:http://maven.apache.org/download.cgi2. Configure Environment variables: 3. Modify the Bin/conf/settings.xml:maven warehouse location under the Maven folder (the default Maven warehouse location is: C:\Users\Administrator\.m2 (where Administrator is the current account). )4. Download Maven plugin: Htt
How MAVEN plug-ins runMaven runs a command with each life cycle, and each life cycle executes to see which plug-ins are configured in the Pom.xml file and then run it.Maven's lifecycle is tied to plug-ins to accomplish actual build tasks. More specifically, the phase of the lifecycle is tied to the goals of the plug-in to accomplish a specific build task. The specific functionality is implemented by the plug-in (P
The plugin's maven dependency is:
The document address of the plugin is:http://www.mojohaus.org/wagon-maven-plugin/
Mainly provides the following several goalWagon:upload-single uploads the specified file to a remote location.Wagon:upload uploads the specified set of files to a remote location.Wagon:download-single d
First, the Environment preparationTwo serversJenkins Server yum install and configure MavenTomcat Server Tomcat version apache-tomcat-8.0.33.tar.gzJDK version jdk-8u77-linux-x64.tar.gzTomcat to deploy the manager project with Tomcat rights supportTomcat Tomcat-users.xml as configured650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/8B/02/wKiom1hBIXOTwpTqAAAMEXLlYZM251.png "title=" Tomcat Configuration "alt=" Wkiom1hbixotwptqaaamexllyzm251.png "/>The username and password here are consis
Reference: http://blog.csdn.net/symgdwyh/article/details/6081532Maven Assembly pluginHttp://maven.apache.org/plugins/maven-assembly-plugin/index.htmlUsageHttp://maven.apache.org/plugins/maven-assembly-plugin/usage.html
Procedure
#1 copy the following code to the Pom. xml file of the
The "Org.springframework.boot:spring-boot-maven-plugin" plugin was added to the OM file. After the plugin is added, when the MVN package is run, it is packaged as a JAR file that can be run directly, and can be run directly using the "Java-jar" command. This simplifies the deployment of the application to a great exten
The Describes how to use the assembly package configuration file before, and here's how to package the entire project into a single executable jar. During system testing, a separate jar is required to test with the other integration team. For the first time, the jar package was chosen with assembly plugin, because our test program was inside Src/test/java, and assembly could automatically pack the test package and test dependencies, as follows: 1. C
Reproduced in: http://nileader.blog.51cto.com/1381108/449956
In the project release, you may encounter this situation, I hope that the project source code to maintain the same premise, you want to be able to target different operating environment to obtain the corresponding running package. (e.g. War pack)
It is possible to use a configuration file to solve this problem. You can put some parameters in the project and the running environment in the configuration file, each environment, so that b
Phenomenon:Eclipse Import existing Maven project, (parent project contains many sub-projects), pom.xml error for subproject:Plugin execution not covered by lifecycle Configuration:org.codehaus.mojo:aspectj-maven-plugin:1.8:compile(Execution:default,phase:compile)Workaround One:Enclose all the plugin tags inside a
The Deploy plugin is the official plugin provided by the Apache Maven team, the latest version of 2.8.2, released in 2014-08-27. The plug-in can deploy the built-in artifacts directly to the remote library of the POM configuration.
By default, the plugin is already configured for use in MAVEN's deploy phase, and the
Failed to execute goal Org. apache. maven. plugins: Maven-shade-plugin: 2.0: shade (default) on Project qmserver: Execution default of Goal Org. apache. maven. plugins: Maven-shade-plugin: 2.0: shade failed: A Required class was m
This article describes how to build a Tomcat Web project in Eclipse through the Tomcat-maven plugin.1. Configuring the Tomcat Manager userOpen Tomcat_user.xml in the Conf directory under the Tomcat root directory, add Manager roles and users under the tomcat-users> 2. Add the Tomcat plugin to the Pom file and configure the Tomcat Server.Open the project Pom.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.