我有一个多模块项目。 我已经在pom.xml中引入了一个属性app.version ，而不是版本中的任何版本：版本标记和模块部分中的依赖项。 
 
 我在哈德逊环境中使用maven 3.1.1。 
 
 用${app.version}替换写入的值（1.6.0-SNAPSHOT）后，真正通过的构建顺序没有出错。 
 
 是什么导致了这个问题 
 
 我从一开始就得到了这些警告，可能会有影响吗？ 
 
[WARNING] Some problems were encountered while building the effective model     for com.mycompany.project:project-module:jar:2.4.0
[WARNING] 'version' contains an expression but should be a constant. @ com.mycompany.project:project-module:${app.version}, /var/lib/hudson/jobs/myJob TRUNK Maven/workspace/project-module/pom.xml, line 20, column 11
 
 我需要解析太多的pom.xml：s，所以层次结构如下，我给它： 
 
main_pom
  |
   --- modules
  |      |
  |       --- all other modules
   --- test        |
                     module A
                   |   |
                   |    module B
                     module C
 
 我给哈德森从main_pom开始。 它最后处理main_pom。 为什么？ 它从所有其他模块部分中的随机一个开始，构建其他模块，然后是模块，测试和main_pom。 为什么这个疯狂的命令？ 
 
 失败在模块A中。它首先构建而不是模块B. 
 
 正确的顺序是从main_pom - >模块B - >模块A等开始，但它直接从模块A开始。 
 
 编辑： 
 
 我的pom.xmls具有以下结构： 
 
 <parent>
    <groupId>com.mycompany.project</groupId>
    <artifactId>modules or parent_pom</artifactId>
    <version>${app.version}</version>
    <relativePath>../modules or parent_pom</relativePath>
 </parent>

<dependency>
    <groupId>com.mycompany.project</groupId>
    <artifactId>some other module</artifactId>
    <version>${app.version}</version>
</dependency>

I have a multi module project. I have introduced a property app.version which I use instead of version everywhere in the pom.xml: in version tag and in dependencies in modules part.
 
I use maven 3.1.1 in Hudson environment.
 
After substituting written values (1.6.0-SNAPSHOT) with ${app.version}, the build order that really goes through without error, is gone.
 
What caused the issue?
 
I got these kind of warnings in the begin, may it affect?
 
[WARNING] Some problems were encountered while building the effective model     for com.mycompany.project:project-module:jar:2.4.0
[WARNING] 'version' contains an expression but should be a constant. @ com.mycompany.project:project-module:${app.version}, /var/lib/hudson/jobs/myJob TRUNK Maven/workspace/project-module/pom.xml, line 20, column 11
 
I would need to parse too much the pom.xml:s, so the hierarchy is like follows, I give it:
 
main_pom
  |
   --- modules
  |      |
  |       --- all other modules
   --- test        |
                     module A
                   |   |
                   |    module B
                     module C
 
I give for hudson to start from main_pom. It handles main_pom as last. Why? It starts now from random one in all other modules part, builds the others, then modules, test and main_pom. Why this insane order?
 
The fail is in module A. It builds that first and not module B.
 
Correct order would be to start from main_pom -> module B -> module A etc but it starts directly from module A.
 
Edit:
 
My pom.xmls have the following structure:
 
 <parent>
    <groupId>com.mycompany.project</groupId>
    <artifactId>modules or parent_pom</artifactId>
    <version>${app.version}</version>
    <relativePath>../modules or parent_pom</relativePath>
 </parent>

<dependency>
    <groupId>com.mycompany.project</groupId>
    <artifactId>some other module</artifactId>
    <version>${app.version}</version>
</dependency>

原文：https://stackoverflow.com/questions/40907845