只有当项目在Eclipse中关闭时，Maven对工作区中项目的依赖才起作用

Question

我正在使用Eclipse开普勒和Maven的M2E插件。

我想用我的“Util”Maven项目创建web app Maven项目——这不是一个多模块项目。我只想要这么简单。jar在项目中，可以在使用主项目的过程中编辑带有增强和修复的“Util”项目。

我在webb应用程序中只添加了maven依赖项（没有构建路径、部署程序集等设置），Eclipse自动发现这是来自工作区的项目（简单地说：不是带有版本号的.jar，而是带有文件夹图标）

现在，当我在maven repo中安装“Util”并关闭项目时，一切正常，Eclipse正在部署我的Util-0.0.1-SNAPSHOT。jar到web inf/lib作为工作。jar文件。

问题是：当打开util项目时，eclipse只会在部署中创建“util.jar”（而不是util-0.0.1-SNAPSHOT.jar），并将其部署为“类似jar的war”，将类放在WEB-INF/classes/中，而不是jar的根目录中，因此我最终得到如下结果：

...\wtpwebapps\BigProject\WEB-INF\lib\util.jar\WEB-INF\类\，结果是简单的ClassNotFoundExctive，因为"Util"项目不是一个Web项目-仅限具有简单类的. jar。

如何在web应用程序中添加对simple util项目的Maven依赖，仍然可以在工作区中随时编辑util项目？

Answer 1

有和你一样的设置，它工作正常。当我在小项目上工作并进行mvn安装时JAR不会作为projName-0.0.1-SNAPSHOT部署在目标位置。尽管如此。两个项目是否有相同的

编辑：我有一些时间，也准备了一些东西，所以我做了一些测试。很抱歉发了这么长的帖子，但这对我来说很有效。我正在使用WildFly服务器。

1/

2a/这是pom。xml的utilsjar

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

<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">

  <!-- =========================================================== -->
  <!-- Basics -->
  <!-- =========================================================== -->

    <modelVersion>4.0.0</modelVersion>
    <groupId>so.examples</groupId>
    <artifactId>utils</artifactId>
    <version>0.0.1</version>
    <packaging>jar</packaging>
    <name>WebApp Common files</name>
    <description>WebApp Common files</description>

  <!-- =========================================================== -->
  <!-- Properties -->
  <!-- =========================================================== -->

    <properties>

        <!-- other plugin versions -->
        <version.compiler.plugin>2.3.2</version.compiler.plugin>
        <version.surefire.plugin>2.4.3</version.surefire.plugin>

        <!-- maven-compiler-plugin -->
        <maven.compiler.target>1.7</maven.compiler.target>

    </properties>


    <dependencyManagement>
        <dependencies>
         </dependencies>
    </dependencyManagement>


    <dependencies>

    </dependencies>

    <build>
        <!-- Maven will append the version to the finalName -->
        <finalName>${project.artifactId}</finalName>


        <plugins>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>${version.compiler.plugin}</version>
                <configuration>
                    <source>${maven.compiler.source}</source>
                    <target>${maven.compiler.target}</target>
                </configuration>
            </plugin>

        </plugins>

    </build>
</project>

2b/和类文件

package utils.commons;


public class PrintUtilities 
{   

    public static String addArrowPrint(String toPrint)
    {
        return "--->"+toPrint+"<----";      
    }
}

3a/这是pom。webApp的xml

<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>so.examples</groupId>
<artifactId>webapp</artifactId>
<packaging>war</packaging>
<version>0.0.1</version>
<description>Main WebApp project</description>


<properties>
    <!-- Explicitly declaring the source encoding eliminates the following
        message: -->
    <!-- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
        resources, i.e. build is platform dependent! -->
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

    <!-- JBoss dependency versions -->
    <version.jboss.maven.plugin>7.4.Final</version.jboss.maven.plugin>

    <!-- Define the version of the JBoss BOMs we want to import to specify
        tested stacks. -->
    <version.jboss.bom>1.0.7.Final</version.jboss.bom>

    <!-- other plugin versions -->
    <version.surefire.plugin>2.10</version.surefire.plugin>
    <version.war.plugin>2.1.1</version.war.plugin>

    <!-- maven-compiler-plugin -->
    <maven.compiler.target>1.7</maven.compiler.target>
    <maven.compiler.source>1.7</maven.compiler.source>
</properties>


<dependencyManagement>
    <dependencies>
        <!-- JBoss distributes a complete set of Java EE 6 APIs including a Bill
            of Materials (BOM). A BOM specifies the versions of a "stack" (or a collection)
            of artifacts. We use this here so that we always get the correct versions
            of artifacts. Here we use the jboss-javaee-6.0-with-tools stack (you can
            read this as the JBoss stack of the Java EE 6 APIs, with some extras tools
            for your project, such as Arquillian for testing) and the jboss-javaee-6.0-with-hibernate
            stack you can read this as the JBoss stack of the Java EE 6 APIs, with extras
            from the Hibernate family of projects) -->
        <dependency>
            <groupId>org.jboss.bom</groupId>
            <artifactId>jboss-javaee-6.0-with-tools</artifactId>
            <version>${version.jboss.bom}</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
        <dependency>
            <groupId>org.jboss.bom</groupId>
            <artifactId>jboss-javaee-6.0-with-hibernate</artifactId>
            <version>${version.jboss.bom}</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

<dependencies>

    <dependency>
        <groupId>so.examples</groupId>
        <artifactId>jar_lib</artifactId>
        <version>0.0.1</version>
    </dependency>

    <!-- First declare the APIs we depend on and need for compilation. All
        of them are provided by JBoss AS 7 -->

    <!-- Import the Common Annotations API (JSR-250), we use provided scope
        as the API is included in JBoss AS 7 -->
    <dependency>
        <groupId>org.jboss.spec.javax.annotation</groupId>
        <artifactId>jboss-annotations-api_1.1_spec</artifactId>
        <scope>provided</scope>
    </dependency>

    <!-- Import the JAX-RS API, we use provided scope as the API is included
        in JBoss AS 7 -->
    <dependency>
        <groupId>org.jboss.spec.javax.ws.rs</groupId>
        <artifactId>jboss-jaxrs-api_1.1_spec</artifactId>
        <scope>provided</scope>
    </dependency>

    <!-- Import the EJB API, we use provided scope as the API is included in
        JBoss AS 7 -->
    <dependency>
        <groupId>org.jboss.spec.javax.ejb</groupId>
        <artifactId>jboss-ejb-api_3.1_spec</artifactId>
        <scope>provided</scope>
    </dependency>


    <!-- Import the JSF API, we use provided scope as the API is included in
        JBoss AS 7 -->
    <dependency>
        <groupId>org.jboss.spec.javax.faces</groupId>
        <artifactId>jboss-jsf-api_2.1_spec</artifactId>
        <scope>provided</scope>
    </dependency>

    <!-- Now we declare any tools needed -->

</dependencies>

<build>
    <!-- Maven will append the version to the finalName (which is the name
        given to the generated war, and hence the context root) -->
    <finalName>${project.artifactId}</finalName>
    <plugins>
        <plugin>
            <artifactId>maven-war-plugin</artifactId>
            <version>${version.war.plugin}</version>
            <configuration>
                <!-- Java EE 6 doesn't require web.xml, Maven needs to catch up! -->
                <failOnMissingWebXml>false</failOnMissingWebXml>
            </configuration>
        </plugin>
        <!-- The JBoss AS plugin deploys your war to a local JBoss AS container -->
        <!-- To use, run: mvn package jboss-as:deploy -->
        <plugin>
            <groupId>org.jboss.as.plugins</groupId>
            <artifactId>jboss-as-maven-plugin</artifactId>
            <version>${version.jboss.maven.plugin}</version>
        </plugin>
        <plugin>
            <groupId>org.wildfly.plugins</groupId>
            <artifactId>wildfly-maven-plugin</artifactId>
            <version>1.0.1.Final</version>
        </plugin>
    </plugins>
</build>

<profiles>
    <profile>
        <!-- The default profile skips all tests, though you can tune it to run
            just unit tests based on a custom pattern -->
        <!-- Seperate profiles are provided for running all tests, including Arquillian
            tests that execute in the specified container -->
        <id>default</id>
        <activation>
            <activeByDefault>true</activeByDefault>
        </activation>
        <build>
            <plugins>
                <plugin>
                    <artifactId>maven-surefire-plugin</artifactId>
                    <version>${version.surefire.plugin}</version>
                    <configuration>
                        <skip>true</skip>
                    </configuration>
                </plugin>
            </plugins>
        </build>
    </profile>


</profiles> 

3b/以下是类文件：

package webapp;


import javax.ws.rs.ApplicationPath;
import javax.ws.rs.core.Application;

@ApplicationPath("/root")
public class RESTActivator extends Application {


}

打包webapp；

import javax.ejb.LocalBean;
import javax.ejb.Stateless;
import javax.ws.rs.*;

import utils.commons.PrintUtilities;

@Stateless
@LocalBean
@Path("/methods")
public class RestMethods  {


    @GET()
    @Produces("text/plain")
    public String welcomeMessage()
    {
        StringBuffer welcomeText = new StringBuffer();

        welcomeText.append(" Called  Rest Methods  \n");
        welcomeText.append(" ====================  \n");
        welcomeText.append(PrintUtilities.addArrowPrint("Called  Rest Methods") + "\n");        

        return welcomeText.toString();
    }
}//class

4/我首先为utils项目做一个mvn清洁安装。在它安装到我本地的maven回购中之后。然后在我的网络应用项目上做一个带有eclipse的更新项目，然后做清洁包野蝇：部署（服务器必须已经启动）。

然后将浏览器指向http://localhost:8080/webapp/root/methods

希望这有帮助。