【第22期】观点:IT 行业加班,到底有没有价值?

如何在基于Eclipse的Maven项目中配置Web Application开发包?

原创 2013年12月03日 16:23:28

以下是一个范例:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    
    <groupId>com.homeland.myapp</groupId>
    <artifactId>myapp</artifactId>
    <packaging>war</packaging>
    <version>0.0.1-SNAPSHOT</version>
    <name>myapp Maven Webapp</name>
    <url>http://maven.apache.org</url>
    
    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <cxf.version>2.7.6</cxf.version>
        <springVersion>3.2.1.RELEASE</springVersion>
        <hibernateVersion>4.1.9.Final</hibernateVersion>
    </properties>
    
    <dependencies>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>4.11</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.hibernate</groupId>
            <artifactId>hibernate-core</artifactId>
            <version>${hibernateVersion}</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-context</artifactId>
            <version>${springVersion}</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-core</artifactId>
            <version>${springVersion}</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-web</artifactId>
            <version>${springVersion}</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-webmvc</artifactId>
            <version>${springVersion}</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-orm</artifactId>
            <version>${springVersion}</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-tx</artifactId>
            <version>${springVersion}</version>
        </dependency>
        <dependency>
            <groupId>org.springframework.ws</groupId>
            <artifactId>spring-ws-core</artifactId>
            <version>2.1.4.RELEASE</version>
        </dependency>
        <dependency>
            <groupId>org.springframework</groupId>
            <artifactId>spring-test</artifactId>
            <version>${springVersion}</version>
        </dependency>
        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>httpcore</artifactId>
            <version>4.3</version>
        </dependency>
        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>httpclient</artifactId>
            <version>4.3</version>
        </dependency>
        <dependency>
            <groupId>antlr</groupId>
            <artifactId>antlr</artifactId>
            <version>2.7.7</version>
        </dependency>
        <dependency>
            <groupId>aopalliance</groupId>
            <artifactId>aopalliance</artifactId>
            <version>1.0</version>
        </dependency>
        <dependency>
            <groupId>org.aspectj</groupId>
            <artifactId>aspectjrt</artifactId>
            <version>1.7.2</version>
        </dependency>
        <dependency>
            <groupId>org.hibernate</groupId>
            <artifactId>hibernate-c3p0</artifactId>
            <version>${hibernateVersion}</version>
        </dependency>
        <dependency>
            <groupId>commons-cli</groupId>
            <artifactId>commons-cli</artifactId>
            <version>1.2</version>
        </dependency>
        <dependency>
            <groupId>commons-codec</groupId>
            <artifactId>commons-codec</artifactId>
            <version>1.6</version>
        </dependency>
        <dependency>
            <groupId>commons-logging</groupId>
            <artifactId>commons-logging</artifactId>
            <version>1.1.3</version>
        </dependency>
        <dependency>
            <groupId>dom4j</groupId>
            <artifactId>dom4j</artifactId>
            <version>1.6.1</version>
        </dependency>
        <dependency>
            <groupId>org.javassist</groupId>
            <artifactId>javassist</artifactId>
            <version>3.15.0-GA</version>
        </dependency>
        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>httpmime</artifactId>
            <version>4.3</version>
        </dependency>
        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>httpcore-nio</artifactId>
            <version>4.3</version>
        </dependency>
        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>httpclient-cache</artifactId>
            <version>4.3</version>
        </dependency>
        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>fluent-hc</artifactId>
            <version>4.3</version>
        </dependency>
        <dependency>
            <groupId>org.apache.httpcomponents</groupId>
            <artifactId>httpcore-ab</artifactId>
            <version>4.3</version>
        </dependency>
        <dependency>
            <groupId>org.codehaus.jackson</groupId>
            <artifactId>jackson-core-asl</artifactId>
            <version>1.9.13</version>
        </dependency>
        <dependency>
            <groupId>org.codehaus.jackson</groupId>
            <artifactId>jackson-mapper-asl</artifactId>
            <version>1.9.13</version>
        </dependency>
        <dependency>
            <groupId>org.codehaus.jackson</groupId>
            <artifactId>jackson-jaxrs</artifactId>
            <version>1.9.13</version>
        </dependency>
        <dependency>
            <groupId>org.jboss.logging</groupId>
            <artifactId>jboss-logging</artifactId>
            <version>3.1.0.GA</version>
        </dependency>
        <dependency>
            <groupId>org.jboss.spec.javax.transaction</groupId>
            <artifactId>jboss-transaction-api_1.1_spec</artifactId>
            <version>1.0.1.Final</version>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>jcl-over-slf4j</artifactId>
            <version>1.6.6</version>
        </dependency>
        <dependency>
            <groupId>org.codehaus.jettison</groupId>
            <artifactId>jettison</artifactId>
            <version>1.3.3</version>
        </dependency>
        <dependency>
            <groupId>log4j</groupId>
            <artifactId>log4j</artifactId>
            <version>1.2.15</version>
            <exclusions>
                <exclusion>
                    <groupId>com.sun.jmx</groupId>
                    <artifactId>jmxri</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>com.sun.jdmk</groupId>
                    <artifactId>jmxtools</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>javax.jms</groupId>
                    <artifactId>jms</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>ch.qos.logback</groupId>
            <artifactId>logback-access</artifactId>
            <version>1.0.13</version>
        </dependency>
        <dependency>
            <groupId>ch.qos.logback</groupId>
            <artifactId>logback-core</artifactId>
            <version>1.0.13</version>
        </dependency>
        <dependency>
            <groupId>com.mchange</groupId>
            <artifactId>mchange-commons-java</artifactId>
            <version>0.2.3.4</version>
        </dependency>
        <dependency>
            <groupId>org.apache.neethi</groupId>
            <artifactId>neethi</artifactId>
            <version>3.0.2</version>
        </dependency>
        <dependency>
            <groupId>org.postgresql</groupId>
            <artifactId>postgresql</artifactId>
            <version>9.2-1003-jdbc4</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
            <version>1.6.6</version>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-log4j12</artifactId>
            <version>1.6.6</version>
        </dependency>
        <dependency>
            <groupId>taglibs</groupId>
            <artifactId>standard</artifactId>
            <version>1.1.2</version>
        </dependency>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>jstl</artifactId>
            <version>1.2</version>
        </dependency>
        <dependency>
            <groupId>commons-digester</groupId>
            <artifactId>commons-digester</artifactId>
            <version>2.1</version>
        </dependency>
        <dependency>
            <groupId>org.apache.derby</groupId>
            <artifactId>derby</artifactId>
            <version>10.10.1.1</version>
        </dependency>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>javax.servlet-api</artifactId>
            <version>3.0.1</version>
        </dependency>
    </dependencies>
    
    <build>
        <finalName>myapp</finalName>
        <plugins>
            <plugin>
                <groupId>org.apache.tomcat.maven</groupId>
                <artifactId>tomcat7-maven-plugin</artifactId>
                <version>2.1</version>
                <configuration>
                    <port>9090</port>
                    <path>/myapp</path>
                    <useTestClassPath>false</useTestClassPath>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>2.3.2</version>
                <configuration>
                    <source>1.7</source>
                    <target>1.7</target>
                </configuration>
            </plugin>
        </plugins>
    </build>
</project>

更多的开发包可以在这个网站中搜索dependency:http://www.mvnrepository.com/

另外,如果你要引用hibernate的包,你需要在你的settings.xml文件做如下修改:

jboss部分

<?xml version="1.0" encoding="UTF-8"?>

<!-- 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 ${user.home}/.m2/settings.xml. | | NOTE: This location 
    can be overridden with the CLI option: | | -s /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 CLI option: | | -gs /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 xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
    <!-- localRepository | The path to the local repository maven will use to store 
        artifacts. | | Default: ${user.home}/.m2/repository <localRepository>/path/to/local/repo</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> -->

    <!-- pluginGroups | This is a list of additional group identifiers that will 
        be searched when resolving plugins by their prefix, i.e. | when invoking a command 
        line like "mvn prefix:goal". Maven will automatically add the group identifiers | 
        "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained 
        in the list. | -->
    <pluginGroups>
        <!-- pluginGroup | Specifies a further group identifier to use for plugin 
            lookup. <pluginGroup>com.your.plugins</pluginGroup> -->
        <pluginGroup>org.jboss.maven.plugins</pluginGroup>
    </pluginGroups>

    <!-- 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> -->
        <server>
            <id>dev-tomcat</id>
            <username>admin</username>
            <password>admin</password>
        </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> -->

        <profile>
            <id>jboss-public-repository</id>
            <repositories>
                <repository>
                    <id>jboss-public-repository-group</id>
                    <name>JBoss Public Maven Repository Group</name>
                    <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>
                    <layout>default</layout>
                    <releases>
                        <enabled>true</enabled>
                        <updatePolicy>never</updatePolicy>
                    </releases>
                    <snapshots>
                        <enabled>true</enabled>
                        <updatePolicy>never</updatePolicy>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>jboss-public-repository-group</id>
                    <name>JBoss Public Maven Repository Group</name>
                    <url>https://repository.jboss.org/nexus/content/groups/public-jboss/</url>
                    <layout>default</layout>
                    <releases>
                        <enabled>true</enabled>
                        <updatePolicy>never</updatePolicy>
                    </releases>
                    <snapshots>
                        <enabled>true</enabled>
                        <updatePolicy>never</updatePolicy>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>
        </profile>


        <profile>
            <id>jboss-deprecated-repository</id>
            <repositories>
                <repository>
                    <id>jboss-deprecated-repository</id>
                    <name>JBoss Deprecated Maven Repository</name>
                    <url>https://repository.jboss.org/nexus/content/repositories/deprecated/</url>
                    <layout>default</layout>
                    <releases>
                        <enabled>true</enabled>
                        <updatePolicy>never</updatePolicy>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                        <updatePolicy>never</updatePolicy>
                    </snapshots>
                </repository>
            </repositories>
        </profile>

    </profiles>

    <!-- activeProfiles | List of profiles that are active for all builds. | <activeProfiles> 
        <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> 
        </activeProfiles> -->
    <activeProfiles>
        <activeProfile>jboss-public-repository</activeProfile>
    </activeProfiles>
</settings>


版权声明:本文为博主原创文章,未经博主允许不得转载。 举报

相关文章推荐

用Maven构建Java Web开发环境(Jetty容器)

Maven是构建Java应用的优秀管理工具,是Apache软件基金会的顶级项目。其具有开发目录构建和管理,统一管理第三方依赖,编译,测试,打包,发布等功能。最大的特点要数第三方依赖管理了,因为其它功能...

使用eclipse和maven一步一步配置web项目

maven是个项目管理工具,集各种功能于一身,下面介绍maven web项目在eclipse种的配置,并于tomcat集成。配置成功后,可以跟一般的web项目一样调试。 一、准备条件 1、安装下载jdk 这里以jdk1.6为例 2、安装eclipse 到eclipse官网下载 E...

程序员升职加薪指南!还缺一个“证”!

CSDN出品,立即查看!

Spring开发包介绍

在建立spring工程的时候,需要引入spring的开发包,否则无法建立spring的开发和运行环境, 以下简单介绍一下spring的核心开发包的基本用途:     spring-core: ...

基于Maven的Spring Spring MVC Mybatis的环境搭建 | AmazingHarry

老大想要做一个TimeSheet的东西,要管理公司员工每年的时间和effort. 反正还要个什么报表,老大发话了,很荣幸我有此机会又可以和刚进公司带我的老大一起做东西了,感觉很好。不过这个项目是一个...
收藏助手
不良信息举报
您举报文章:深度学习:神经网络中的前向传播和反向传播算法推导
举报原因:
原因补充:

(最多只允许输入30个字)