- 浏览: 165726 次
- 性别:
- 来自: 上海
文章分类
最新评论
-
wanglikun521521:
spring4也一样
spring配置文件异常 -
lixunhui:
废话,。第二个你试过没有,确定可以显示Administrato ...
windows xp 中的administrator帐户不在用户登录内怎么解决? -
wanmeinange:
如果里面的jar包。没有用maven呢?直接引入的jar。这种 ...
spring配置文件异常 -
onlydo:
如果没有把程序都打包到一个jar包里面是不会有这个问题。
spring配置文件异常 -
fjjiaboming:
显然这种方式不适合 spring 3.x
spring配置文件异常
1. 下载解压到指定目录,并设置环境变量M2_HOME,并把bin添加到PATH变量中。
2. 修改本地repo,修改maven-home/conf/settings.xml文件
内容如下:
3.安装MAVEN的eclispe插件,配置repo地址。
* 还不能删除~home/.m2/settings.xml文件,否则插件用不起来。同样办法修改这个文件,让repo指定到上面那个地址。
4.未找到的jar安装方法,比如jta,这个包在官方的repo中一般都没有。自己找个来安装到本地的repo中。
mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file
5.私服建立,google:artifactory
6.checksum文件生成。
显示一个插件所有的goal
创建一个基于模版的项目,eclipse项目
//创建标准目录模板
mvn archetype:create -DgroupId=com.codeline.commons -DartifactId=codelineCommons
//创建web项目
mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-web
查看一个插件所用的版本
mvn -Dplugin=groupId:artifactId help:describe
忽略编译test
mvn -Dmaven.test.skip=true
一个jar文件,它是maven的一个插件,怎么安装到本地库。
mvn install:install-file
-Dfile=<path-to-file>
-DgroupId=<group-id>
-DartifactId=<artifact-id>
-Dversion=<version>
-Dpackaging=<packaging>
-DgeneratePom=true
maven的生命周期
validate,验证工程是否正确,所有需要的资源是否可用。
compile,编译项目的源代码。
test-compile,编译项目测试代码。
test,使用已编译的测试代码,测试已编译的源代码。
package,已发布的格式,如jar,将已编译的源代码打包。
integration-test,在集成测试可以运行的环境中处理和发布包。
verify,运行任何检查,验证包是否有效且达到质量标准。
install,把包安装在本地的repository中,可以被其他工程作为依赖来使用
deploy,在整合或者发布环境下执行,将最终版本的包拷贝到远程的repository,使得其他的开发者或者工程可以共享。
generate-sources,产生应用需要的任何额外的源代码,如xdoclet。
Dependency Scope
compile,缺省值,适用于所有阶段,会随着项目一起发布。
provided,类似compile,期望JDK、容器或使用者会提供这个依赖。如servlet.jar。
runtime,只在运行时使用,如JDBC驱动,适用运行和测试阶段。
test,只在测试时使用,用于编译和运行测试代码。不会随项目发布。
system,类似provided,需要显式提供包含依赖的jar,Maven不会在Repository中查找它
eg:
<dependency>
<groupId>hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.0.3</version>
<scope>test</scope>
</dependency>
2. 修改本地repo,修改maven-home/conf/settings.xml文件
内容如下:
<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- | This is the configuration file for Maven. It can be specified at two levels: | | 1. User Level. This settings.xml file provides configuration for a single user, | and is normally provided in $HOME/.m2/settings.xml. | | NOTE: This location can be overridden with the system property: | | -Dorg.apache.maven.user-settings=/path/to/user/settings.xml | | 2. Global Level. This settings.xml file provides configuration for all maven | users on a machine (assuming they're all using the same maven | installation). It's normally provided in | ${maven.home}/conf/settings.xml. | | NOTE: This location can be overridden with the system property: | | -Dorg.apache.maven.global-settings=/path/to/global/settings.xml | | The sections in this sample file are intended to give you a running start at | getting the most out of your Maven installation. Where appropriate, the default | values (values used when the setting is not specified) are provided. | |--> <settings> <!-- localRepository | The path to the local repository maven will use to store artifacts. | | Default: ~/.m2/repository --> <localRepository>D:\installed\maven-2.0.7\repository</localRepository> <!-- interactiveMode | This will determine whether maven prompts you when it needs input. If set to false, | maven will use a sensible default value, perhaps based on some other setting, for | the parameter in question. | | Default: true <interactiveMode>true</interactiveMode> --> <!-- offline | Determines whether maven should attempt to connect to the network when executing a build. | This will have an effect on artifact downloads, artifact deployment, and others. | | Default: false <offline>false</offline> --> <!-- proxies | This is a list of proxies which can be used on this machine to connect to the network. | Unless otherwise specified (by system property or command-line switch), the first proxy | specification in this list marked as active will be used. |--> <proxies> <!-- proxy | Specification for one proxy, to be used in connecting to the network. | <proxy> <id>optional</id> <active>true</active> <protocol>http</protocol> <username>proxyuser</username> <password>proxypass</password> <host>proxy.host.net</host> <port>80</port> <nonProxyHosts>local.net,some.host.com</nonProxyHosts> </proxy> --> </proxies> <!-- servers | This is a list of authentication profiles, keyed by the server-id used within the system. | Authentication profiles can be used whenever maven must make a connection to a remote server. |--> <servers> <!-- server | Specifies the authentication information to use when connecting to a particular server, identified by | a unique name within the system (referred to by the 'id' attribute below). | | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are | used together. | <server> <id>deploymentRepo</id> <username>repouser</username> <password>repopwd</password> </server> --> <!-- Another sample, using keys to authenticate. <server> <id>siteServer</id> <privateKey>/path/to/private/key</privateKey> <passphrase>optional; leave empty if not used.</passphrase> </server> --> </servers> <!-- mirrors | This is a list of mirrors to be used in downloading artifacts from remote repositories. | | It works like this: a POM may declare a repository to use in resolving certain artifacts. | However, this repository may have problems with heavy traffic at times, so people have mirrored | it to several places. | | That repository definition will have a unique id, so we can create a mirror reference for that | repository, to be used as an alternate download site. The mirror site will be the preferred | server for that repository. |--> <mirrors> <!-- mirror | Specifies a repository mirror site to use instead of a given repository. The repository that | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used | for inheritance and direct lookup purposes, and must be unique across the set of mirrors. | <mirror> <id>mirrorId</id> <mirrorOf>repositoryId</mirrorOf> <name>Human Readable Name for this Mirror.</name> <url>http://my.repository.com/repo/path</url> </mirror> --> </mirrors> <!-- profiles | This is a list of profiles which can be activated in a variety of ways, and which can modify | the build process. Profiles provided in the settings.xml are intended to provide local machine- | specific paths and repository locations which allow the build to work in the local environment. | | For example, if you have an integration testing plugin - like cactus - that needs to know where | your Tomcat instance is installed, you can provide a variable here such that the variable is | dereferenced during the build process to configure the cactus plugin. | | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles | section of this document (settings.xml) - will be discussed later. Another way essentially | relies on the detection of a system property, either matching a particular value for the property, | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'. | Finally, the list of active profiles can be specified directly from the command line. | | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact | repositories, plugin repositories, and free-form properties to be used as configuration | variables for plugins in the POM. | |--> <profiles> <!-- profile | Specifies a set of introductions to the build process, to be activated using one or more of the | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/> | or the command line, profiles have to have an ID that is unique. | | An encouraged best practice for profile identification is to use a consistent naming convention | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc. | This will make it more intuitive to understand what the set of introduced profiles is attempting | to accomplish, particularly when you only have a list of profile id's for debug. | | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo. <profile> <id>jdk-1.4</id> <activation> <jdk>1.4</jdk> </activation> <repositories> <repository> <id>jdk14</id> <name>Repository for JDK 1.4 builds</name> <url>http://www.myhost.com/maven/jdk14</url> <layout>default</layout> <snapshotPolicy>always</snapshotPolicy> </repository> </repositories> </profile> --> <!-- | Here is another profile, activated by the system property 'target-env' with a value of 'dev', | which provides a specific path to the Tomcat instance. To use this, your plugin configuration | might hypothetically look like: | | ... | <plugin> | <groupId>org.myco.myplugins</groupId> | <artifactId>myplugin</artifactId> | | <configuration> | <tomcatLocation>${tomcatPath}</tomcatLocation> | </configuration> | </plugin> | ... | | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to | anything, you could just leave off the <value/> inside the activation-property. | <profile> <id>env-dev</id> <activation> <property> <name>target-env</name> <value>dev</value> </property> </activation> <properties> <tomcatPath>/path/to/tomcat/instance</tomcatPath> </properties> </profile> --> </profiles> <!-- activeProfiles | List of profiles that are active for all builds. | <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> </activeProfiles> --> </settings>
3.安装MAVEN的eclispe插件,配置repo地址。
* 还不能删除~home/.m2/settings.xml文件,否则插件用不起来。同样办法修改这个文件,让repo指定到上面那个地址。
4.未找到的jar安装方法,比如jta,这个包在官方的repo中一般都没有。自己找个来安装到本地的repo中。
mvn install:install-file -DgroupId=javax.transaction -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar -Dfile=/path/to/file
5.私服建立,google:artifactory
6.checksum文件生成。
<target name="checksum" description="Generate checksum file for jar and pom"> <checksum algorithm="SHA" fileext=".sha1"> <fileset dir="d:/javalib" id="id"> <!--—-jar和pom所在目录 --> <include name="**/*.pom" /> <include name="**/*.jar" /> <include name="**/*.xml" /> <exclude name="**/*.sh1" /> <!--</span-->fileset> <!--</span-->checksum> <!--</span-->target>
显示一个插件所有的goal
创建一个基于模版的项目,eclipse项目
//创建标准目录模板
mvn archetype:create -DgroupId=com.codeline.commons -DartifactId=codelineCommons
//创建web项目
mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp -DarchetypeArtifactId=maven-archetype-web
查看一个插件所用的版本
mvn -Dplugin=groupId:artifactId help:describe
忽略编译test
mvn -Dmaven.test.skip=true
一个jar文件,它是maven的一个插件,怎么安装到本地库。
mvn install:install-file
-Dfile=<path-to-file>
-DgroupId=<group-id>
-DartifactId=<artifact-id>
-Dversion=<version>
-Dpackaging=<packaging>
-DgeneratePom=true
maven的生命周期
validate,验证工程是否正确,所有需要的资源是否可用。
compile,编译项目的源代码。
test-compile,编译项目测试代码。
test,使用已编译的测试代码,测试已编译的源代码。
package,已发布的格式,如jar,将已编译的源代码打包。
integration-test,在集成测试可以运行的环境中处理和发布包。
verify,运行任何检查,验证包是否有效且达到质量标准。
install,把包安装在本地的repository中,可以被其他工程作为依赖来使用
deploy,在整合或者发布环境下执行,将最终版本的包拷贝到远程的repository,使得其他的开发者或者工程可以共享。
generate-sources,产生应用需要的任何额外的源代码,如xdoclet。
Dependency Scope
compile,缺省值,适用于所有阶段,会随着项目一起发布。
provided,类似compile,期望JDK、容器或使用者会提供这个依赖。如servlet.jar。
runtime,只在运行时使用,如JDBC驱动,适用运行和测试阶段。
test,只在测试时使用,用于编译和运行测试代码。不会随项目发布。
system,类似provided,需要显式提供包含依赖的jar,Maven不会在Repository中查找它
eg:
<dependency>
<groupId>hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.0.3</version>
<scope>test</scope>
</dependency>
发表评论
-
Maven生成可执行程序插件使用
2010-09-09 17:20 1310pom插件配置文件添加如下: <plugin> ... -
maven install
2010-05-31 18:04 1194mvn install:install-file -Dfile ... -
maven在eclipse中使用aspectj
2009-12-24 13:11 1062<plugin> <group ... -
svn服务器配置
2009-12-03 17:06 13871.服务器程序安装 svn服务器端程序下载地址: http:/ ... -
Maven使用
2007-12-19 22:55 2615清理依赖 mvn clean dependency:copy- ... -
简单build.xml
2007-08-23 17:10 1327<?xml version="1.0" ... -
eclipse插件
2007-08-22 09:57 1103svn updateurl:http://subclipse ... -
CVS服务器搭建(windows)
2007-08-22 09:51 1598下载安装cvsnt 进控制台init repositor ...
相关推荐
maven使用文档,maven使用文档 很不错的文档
该文档内容从下载 安装 配置环境都有。 除此之外还将idea和maven的一些快捷键,一些idea设置,maven使用等内容, 内容还不错。
maven使用指南
Maven使用tomcat8-maven-plugin插件
Maven 使用入门.pdf
maven入门教程,maven是一个有用的构建工具,把源代码构建成可发布构件的工具,值得一学。
Maven使用手册,介绍了maven的一些日常使用和配置
Maven使用简介
Maven使用
maven使用说明文档 maven使用说明文档 maven使用说明文档
maven使用及Nexus搭建Maven私服
Maven使用实战-从入门到精通实践【张振华.Jack】 Maven简介、Maven主要做什么用? 项目对象模型(POM) 坐标(Coordinates)、打包方式(Packaging)、项目描述 项目子父级关系(parent) 依赖管理(dependency),冲突了...
Maven使用讲解.ppt Maven简介及安装 Maven基本使用 Maven基本概念 POM介绍 Maven多模块项目 Maven插件应用 Maven仓库
maven 使用入门第三章,只有第三章技术文档资料。
Maven的使用教程,其中包括:maven项目开发中的问题及解决方案,maven安装与配置等
Maven使用方法
Maven简单使用说明
Maven 是一个项目管理和构建自动化工具,Maven项目对象模型(POM),可以通过一小段描述信息来管理项目的构建,报告和文档的项目管理工具软件。
maven入门使用,很详细. 本文档介绍一些在使用Maven过程中不是必须的,但十分有用的实践。