blocks|key|1526403|text|你试过../../env_${env}.properties吗？|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1526404|通常，当module2与子模块处于同一级别时，我们会执行以下操作|1526405|<modules>
++++<module>../sub-module1</module>
++++<module>../sub-module2</module>
++++<module>../sub-module3</module>
</modules>|code-block|syntax|javascript|1526406|我认为../..会让你跳上两个层次。如果没有，您可能需要联系插件的作者，看看这是否是一个已知的问题。|1526407|entityMap^0|3|R|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

Did you try <code>../../env_${env}.properties</code> ?

Normally we do the following when module2 is on the same level as the sub-modules

<pre><code>&lt;modules&gt;
 &lt;module&gt;../sub-module1&lt;/module&gt;
 &lt;module&gt;../sub-module2&lt;/module&gt;
 &lt;module&gt;../sub-module3&lt;/module&gt;
&lt;/modules&gt;
</code></pre>

I would think the ../.. would let you jump up two levels. If not, you might want to contact the plug in authors and see if this is a known issue.

blocks|key|1526467|text|我找到了一个解决方案来解决我的问题:我使用Groovy+Maven插件搜索属性文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1526468|由于我的属性文件必须在当前目录中，所以我编写了一小段Groovy代码来检查这三个文件夹。|1526469|下面是我的pom.xml的摘录：|1526470|
<plugin>
++++<groupId>org.codehaus.groovy.maven</groupId>
++++<artifactId>gmaven-plugin</artifactId>
++++<version>1.0-rc-5</version>
++++<executions>
++++++++<execution>
++++++++++++<phase>validate</phase>
++++++++++++<goals>
++++++++++++++++<goal>execute</goal>
++++++++++++</goals>
++++++++++++<configuration>
++++++++++++++++<source>
++++++++++++++++++++import+java.io.File;
++++++++++++++++++++String+p+=+project.properties['env-properties-file'];
++++++++++++++++++++File+f+=+new+File(p);+
++++++++++++++++++++if+(!f.exists())+{
++++++++++++++++++++++++f+=+new+File("../"+%2B+p);
++++++++++++++++++++++++if+(!f.exists())+{
++++++++++++++++++++++++++++f+=+new+File("../../"+%2B+p);
++++++++++++++++++++++++}
++++++++++++++++++++}
++++++++++++++++++++project.properties['env-properties-file-by-groovy']+=+f.getAbsolutePath();
++++++++++++</source>
++++++++++++</configuration>
++++++++</execution>
++++</executions>
</plugin>

<plugin>
++++<groupId>org.codehaus.mojo</groupId>
++++<artifactId>properties-maven-plugin</artifactId>
++++<version>1.0-alpha-1</version>
++++<executions>
++++++++<execution>
++++++++++++<phase>initialize</phase>
++++++++++++<goals>
++++++++++++++++<goal>read-project-properties</goal>
++++++++++++</goals>
++++++++++++<configuration>
++++++++++++++++<files>
++++++++++++++++++++<file>${env-properties-file-by-groovy}</file>
++++++++++++++++</files>
++++++++++++</configuration>
++++++++</execution>
++++</executions>
</plugin>|code-block|syntax|javascript|1526471|这是有效的，但我真的不喜欢它。|1526472|所以，如果你有更好的解决方案，请不要犹豫。|1526473|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I've found a solution to solve my problem: I search the properties files using the Groovy Maven plugin.

As my properties file is necessarily in current directory, in ../ or in ../.., I wrote a small Groovy code that checks these three folders.

Here is the extract of my pom.xml:

<pre><code>&lt;!-- Use Groovy to search the location of the properties file. --&gt;
&lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.groovy.maven&lt;/groupId&gt;
 &lt;artifactId&gt;gmaven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.0-rc-5&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;validate&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;execute&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;source&gt;
 import java.io.File;
 String p = project.properties['env-properties-file'];
 File f = new File(p); 
 if (!f.exists()) {
 f = new File("../" + p);
 if (!f.exists()) {
 f = new File("../../" + p);
 }
 }
 project.properties['env-properties-file-by-groovy'] = f.getAbsolutePath();
 &lt;/source&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
&lt;!-- Now, I can load the properties file using the new 'env-properties-file-by-groovy' property. --&gt;
&lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
 &lt;artifactId&gt;properties-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.0-alpha-1&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;initialize&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;read-project-properties&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;files&gt;
 &lt;file&gt;${env-properties-file-by-groovy}&lt;/file&gt;
 &lt;/files&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

This is working, but I don't really like it.

So, if you have a better solution, do not hesitate to post!

blocks|key|1526521|text|尝试在每个pom中设置一个属性，以找到主项目目录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1526522|在父级中：|1526523|<properties>
++++<main.basedir>${project.basedir}</main.basedir>
</properties>|code-block|syntax|javascript|1526524|在孩子们身上：|1526525|<properties>
++++<main.basedir>${project.parent.basedir}</main.basedir>
</properties>|1526526|在孙子辈中：|1526527|<properties>
++++<main.basedir>${project.parent.parent.basedir}</main.basedir>
</properties>|1526528|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Try setting a property in each pom to find the main project directory. 

In the parent: 

<pre><code>&lt;properties&gt;
 &lt;main.basedir&gt;${project.basedir}&lt;/main.basedir&gt;
&lt;/properties&gt;
</code></pre>

In the children: 

<pre><code>&lt;properties&gt;
 &lt;main.basedir&gt;${project.parent.basedir}&lt;/main.basedir&gt;
&lt;/properties&gt;
</code></pre>

In the grandchildren: 

<pre><code>&lt;properties&gt;
 &lt;main.basedir&gt;${project.parent.parent.basedir}&lt;/main.basedir&gt;
&lt;/properties&gt;
</code></pre>

blocks|key|1311468|text|在answer+to+another+question中，我展示了如何扩展maven-properties-plugin以使用在Maven依赖中定义的外部属性描述符。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1311469|您可以将这一想法扩展为拥有多个描述符JAR，每个描述符JAR的环境名称都是包含${env}.properties的artifactId的一部分。然后，您可以使用该属性选择适当的jar和属性文件，例如：|1311470|<plugin>
++<groupId>org.codehaus.mojo</groupId>
++<artifactId>properties-ext-maven-plugin</artifactId>
++<version>0.0.1</version>
++<executions>
++++<execution>
++++++<id>read-properties</id>
++++++<phase>initialize</phase>
++++++<goals>
++++++++<goal>read-project-properties</goal>
++++++</goals>
++++</execution>
++</executions>++++++++++++++++++++++++++++++
++<configuration>
++++<filePaths>
++++++
++++++<filePath>${env}.properties</filePath>
++++</filePaths>
++</configuration>+
++<dependencies>
++++
++++<dependency>
++++++<groupId>some.descriptor.group</groupId>
++++++<artifactId>env-${env}-descriptor</artifactId>
++++++<version>0.0.1</version>
++++</dependency>
++</dependencies>
</plugin>|code-block|syntax|javascript|1311471|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1231561/how-to-share-common-properties-among-several-maven-projects/1265428#1265428^0|1|Q|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

In an <a href="https://stackoverflow.com/questions/1231561/how-to-share-common-properties-among-several-maven-projects/1265428#1265428">answer to another question</a> I showed how the maven-properties-plugin could be extended to use external property descriptors defined in Maven dependencies.

You could extend that idea to have multiple descriptor jars, each with the environment name as part of the artifactId, containing a ${env}.properties. Then you can use the property to select the appropriate jar and properties file, for example:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
 &lt;artifactId&gt;properties-ext-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;0.0.1&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;read-properties&lt;/id&gt;
 &lt;phase&gt;initialize&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;read-project-properties&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt; 
 &lt;configuration&gt;
 &lt;filePaths&gt;
 &lt;!--assume the descriptor project has a file in the root of the jar --&gt;
 &lt;filePath&gt;${env}.properties&lt;/filePath&gt;
 &lt;/filePaths&gt;
 &lt;/configuration&gt; 
 &lt;dependencies&gt;
 &lt;!-- reference the properties jar for the particular environment--&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;some.descriptor.group&lt;/groupId&gt;
 &lt;artifactId&gt;env-${env}-descriptor&lt;/artifactId&gt;
 &lt;version&gt;0.0.1&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|1526611|text|<plugins>
++<plugin>
++++<groupId>org.codehaus.groovy.maven</groupId>
++++<artifactId>gmaven-plugin</artifactId>
++++<version>1.0</version>
++++<executions>
++++++<execution>
++++++++<phase>validate</phase>
++++++++<goals>
++++++++++<goal>execute</goal>
++++++++</goals>
++++++++<configuration>
++++++++++<source>
++++++++++++import+java.io.File
++++++++++++project.properties.parentdir+=+"${pom.basedir}"
++++++++++++while+(new+File(new+File(project.properties.parentdir).parent,+'pom.xml').exists())+{
++++++++++++++++project.properties.parentdir+=+new+File(project.properties.parentdir).parent
++++++++++++}
++++++++++</source>
++++++++</configuration>
++++++</execution>
++++</executions>
++</plugin>
++<plugin>
++++<groupId>org.codehaus.mojo</groupId>
++++<artifactId>properties-maven-plugin</artifactId>
++++<version>1.0-alpha-2</version>
++++<executions>
++++++<execution>
++++++++<phase>initialize</phase>
++++++++<goals>
++++++++++<goal>read-project-properties</goal>
++++++++</goals>
++++++++<configuration>
++++++++++<files>
++++++++++++<file>${parentdir}/build.properties</file>
++++++++++</files>
++++++++</configuration>
++++++</execution>
++++</executions>
++</plugin>
++...|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1526612|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>&lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.groovy.maven&lt;/groupId&gt;
 &lt;artifactId&gt;gmaven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.0&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;validate&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;execute&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;source&gt;
 import java.io.File
 project.properties.parentdir = "${pom.basedir}"
 while (new File(new File(project.properties.parentdir).parent, 'pom.xml').exists()) {
 project.properties.parentdir = new File(project.properties.parentdir).parent
 }
 &lt;/source&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
 &lt;artifactId&gt;properties-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.0-alpha-2&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;initialize&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;read-project-properties&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;files&gt;
 &lt;file&gt;${parentdir}/build.properties&lt;/file&gt;
 &lt;/files&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 ...
</code></pre>

blocks|key|1311585|text|我认为，如果您将示例中使用的扩展模式用于findbugs、plugin和multimodule，则可以设置与绝对路径相关的全局属性。它使用了一个顶部|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1311586|example+for+multi+module|offset|length|1311587|顶层pom有一个不相关的build-config项目和一个用于多模块项目的模块的app-parent。父应用程序使用扩展将其自身链接到build-config项目并从中获取资源。这用于将公共配置文件传送到模块。它也可能是属性的管道。您可以将顶级目录写入build-config使用的属性文件。(看起来太复杂了)|1311588|问题是，必须在多模块项目中添加一个新的顶层才能使其正常工作。我试图回避一个真正不相关的build-config项目，但它显得笨拙而脆弱。|1311589|entityMap|0|LINK|mutability|MUTABLE|url|http://mojo.codehaus.org/findbugs-maven-plugin/2.1-SNAPSHOT/examples/multi-module-config.html^0|0|0|O|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I think that if you use the extension pattern used in the example for findbugs plugin &amp; multimodule you may be able to set global properties related to absolute paths. It uses a top

<a href="http://mojo.codehaus.org/findbugs-maven-plugin/2.1-SNAPSHOT/examples/multi-module-config.html" rel="nofollow noreferrer">example for multi module</a>

The top level pom has an unrelated build-config project and a app-parent for the modules of the multimodule project. The app-parent uses extension to link itself to the build-config project and obtain resources from it. This is used to carry common config files to the modules. It may be a conduit for properties as well. You could write the top dir to a property file consumed by the build-config. (it seems too complex)

The problem is that a new top level must be added to the multi-module project to make this work. I tried to side step with a truly unrelated build-config project but it was kludgy and seemed brittle.

blocks|key|1311635|text|我只是改进了上面的groovy脚本，以便在根父级属性文件中写入属性：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1311636|import+java.io.*;
String+p+=+project.properties['env-properties-file']
File+f+=+new+File(p)
if+(f.exists())+{
try{
FileWriter+fstream+=+new+FileWriter(f.getAbsolutePath())
BufferedWriter+out+=+new+BufferedWriter(fstream)
String+propToSet+=+f.getAbsolutePath().substring(0,+f.getAbsolutePath().lastIndexOf(File.separator))
if+(File.separator+!=+"/")+{
propToSet+=+propToSet.replace(File.separator,File.separator%2BFile.separator%2BFile.separator)
}
out.write("jacoco.agent+=+"+%2B+propToSet+%2B+"/lib/jacocoagent.jar")
out.close()
}catch+(Exception+e){
}
}
String+ret+=+"../"
while+(!f.exists())+{
f+=+new+File(ret+%2B+p)
ret%2B=+"../"
}
project.properties['env-properties-file-by-groovy']+=+f.getAbsolutePath()|code-block|syntax|javascript|1311637|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I just improve the groovy script from above to write the property in the root parent properties file:

<pre><code>import java.io.*;
String p = project.properties['env-properties-file']
File f = new File(p)
if (f.exists()) {
try{
FileWriter fstream = new FileWriter(f.getAbsolutePath())
BufferedWriter out = new BufferedWriter(fstream)
String propToSet = f.getAbsolutePath().substring(0, f.getAbsolutePath().lastIndexOf(File.separator))
if (File.separator != "/") {
propToSet = propToSet.replace(File.separator,File.separator+File.separator+File.separator)
}
out.write("jacoco.agent = " + propToSet + "/lib/jacocoagent.jar")
out.close()
}catch (Exception e){
}
}
String ret = "../"
while (!f.exists()) {
f = new File(ret + p)
ret+= "../"
}
project.properties['env-properties-file-by-groovy'] = f.getAbsolutePath()
</code></pre>

blocks|key|1311662|text|我找到了解决这个问题的方法:使用${parent.relativePath}|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1311663|<parent>
++++<artifactId>xxx</artifactId>
++++<groupId>xxx</groupId>
++++<version>1.0-SNAPSHOT</version>
++++<relativePath>..</relativePath>
</parent>
<build>
++++<filters>
++++++++<filter>${parent.relativePath}/src/main/filters/filter-${env}.properties</filter>
++++</filters>
++++<resources>
++++++++<resource>
++++++++++++<directory>src/main/resources</directory>
++++++++++++<filtering>true</filtering>
++++++++</resource>
++++</resources>
</build>|code-block|syntax|javascript|1311664|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I've found a solution to solve this problem: 
use ${parent.relativePath}

<pre><code>&lt;parent&gt;
 &lt;artifactId&gt;xxx&lt;/artifactId&gt;
 &lt;groupId&gt;xxx&lt;/groupId&gt;
 &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;
 &lt;relativePath&gt;..&lt;/relativePath&gt;
&lt;/parent&gt;
&lt;build&gt;
 &lt;filters&gt;
 &lt;filter&gt;${parent.relativePath}/src/main/filters/filter-${env}.properties&lt;/filter&gt;
 &lt;/filters&gt;
 &lt;resources&gt;
 &lt;resource&gt;
 &lt;directory&gt;src/main/resources&lt;/directory&gt;
 &lt;filtering&gt;true&lt;/filtering&gt;
 &lt;/resource&gt;
 &lt;/resources&gt;
&lt;/build&gt;
</code></pre>

blocks|key|1311735|text|所以我所看到的问题是，你不能在maven中获得父目录的绝对路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1311736|I've+heard+this+talked+about+as+an+anti-pattern，但是每个反模式都有真实的、合法的用例，我已经厌倦了maven告诉我我只能遵循他们的模式。|offset|length|1311737|所以我找到的解决办法是使用antrun。在子pom.xml中尝试以下内容：|1311738|<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-antrun-plugin</artifactId>
++++<version>1.7</version>
++++<executions>
++++++++<execution>
++++++++++++<id>getMainBaseDir</id>
++++++++++++<phase>validate</phase>
++++++++++++<goals>
++++++++++++++++<goal>run</goal>
++++++++++++</goals>
++++++++++++<configuration>
++++++++++++++++<exportAntProperties>true</exportAntProperties>
++++++++++++++++<target>
++++++++++++++++++++
++++++++++++++++++++<property+name="main.basedir"+location="./.."+/>
++++++++++++++++++++<echo+message="main.basedir=${main.basedir}"/>
++++++++++++++++</target>
++++++++++++</configuration>
++++++++</execution>
++++</executions>
</plugin>|code-block|syntax|javascript|1311739|如果您运行mvn+verify，您应该会看到如下所示：|style|CODE|1311740|main:
+++++[echo]+main.basedir=C:\src\parent.project.dir.name|1311741|然后你可以在任何其他插件中使用${main.basedir}，等等。我花了一段时间才弄明白这一点，所以希望它能对其他人有所帮助。|1311742|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.40175.n5.nabble.com/Relative-path-to-parent-directory-at-multi-module-maven-project-td4611798.html^0|0|0|1B|0|0|0|0|5|A|0|0|F|F|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|18|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|19|8|@$D|1A|E|1B|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|J|7|1C|8|@]|9|@]|A|$K|L]]|$1|S|3|T|5|6|7|1D|8|@$D|1E|E|1F|O|P]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

So the problem as I see it is that you can't get the absolute path to a parent directory in maven.

&lt;rant&gt; <a href="http://maven.40175.n5.nabble.com/Relative-path-to-parent-directory-at-multi-module-maven-project-td4611798.html">I've heard this talked about as an anti-pattern</a>, but for every anti-pattern there is real, legitimate use case for it, and I'm sick of maven telling me I can only follow their patterns.&lt;/rant&gt;

So the work around I found was to use antrun. Try this in the child pom.xml:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.7&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;getMainBaseDir&lt;/id&gt;
 &lt;phase&gt;validate&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;run&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;exportAntProperties&gt;true&lt;/exportAntProperties&gt;
 &lt;target&gt;
 &lt;!--Adjust the location below to your directory structure --&gt;
 &lt;property name="main.basedir" location="./.." /&gt;
 &lt;echo message="main.basedir=${main.basedir}"/&gt;
 &lt;/target&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

If you run <code>mvn verify</code> you should see something like this:

<pre><code>main:
 [echo] main.basedir=C:\src\parent.project.dir.name
</code></pre>

You can then use <code>${main.basedir}</code> in any of the other plugins, etc. Took me a while to figure this out, so hope it helps someone else.

blocks|key|1311801|text|在我的例子中，它是这样工作的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1311802|...
<properties>
++<main_dir>${project.parent.relativePath}/..</main_dir>
</properties>
...

<plugin>
++++++++<groupId>org.codehaus.mojo</groupId>
++++++++<artifactId>properties-maven-plugin</artifactId>
++++++++<version>1.0-alpha-1</version>
++++++++<executions>
++++++++++<execution>
++++++++++++<phase>initialize</phase>
++++++++++++<goals>
++++++++++++++<goal>read-project-properties</goal>
++++++++++++</goals>
++++++++++++<configuration>
++++++++++++++<files>
+++++++++++++++++<file>${main_dir}/maven_custom.properties</file>
++++++++++++++</files>
++++++++++++</configuration>
++++++++++</execution>
++++++++</executions>
</plugin>|code-block|syntax|javascript|1311803|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In my case it works like this:

<pre class="lang-xml prettyprint-override"><code>...
&lt;properties&gt;
 &lt;main_dir&gt;${project.parent.relativePath}/..&lt;/main_dir&gt;
&lt;/properties&gt;
...

&lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
 &lt;artifactId&gt;properties-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.0-alpha-1&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;initialize&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;read-project-properties&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;files&gt;
 &lt;file&gt;${main_dir}/maven_custom.properties&lt;/file&gt;
 &lt;/files&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|1526963|text|您在项目C中，项目C是B的子模块，B是A的子模块。您尝试从项目C访问模块D的src/test/config/etc目录。D也是A的子模块。下面的表达式使获取URI路径成为可能：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1526964|-Dparameter=file:/${basedir}/../../D/src/test/config/etc|code-block|syntax|javascript|1526965|entityMap^0|12|J|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

You are in project C, project C is submodule of B and B is submodule of A. You try to reach module D's <code>src/test/config/etc</code> directory from project C. D is also submodule of A. The following expression makes this possible to get the URI path:

<pre><code>-Dparameter=file:/${basedir}/../../D/src/test/config/etc
</code></pre>

blocks|key|1527023|text|下面这个小简介对我很有效。我需要对CheckStyle进行这样的配置，我将它放到了项目根目录的config目录中，这样我就可以从主模块和子模块运行它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1527024|<profile>
++++<id>root-dir</id>
++++<activation>
++++++++<file>
++++++++++++<exists>${project.basedir}/../../config/checkstyle.xml</exists>
++++++++</file>
++++</activation>
++++<properties>
++++++++<project.config.path>${project.basedir}/../config</project.config.path>
++++</properties>
</profile>|code-block|syntax|javascript|1527025|它不适用于嵌套模块，但我确信可以使用几个带有不同exists的配置文件对其进行修改。(我不知道为什么在验证标记中应该有"../..“，而在被覆盖的属性本身中只有"..”，但它只能以这种方式工作。)|1527026|entityMap^0|1B|6|0|0|O|6|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

The following small profile worked for me. I needed such a configuration for CheckStyle, which I put into the <code>config</code> directory in the root of the project, so I can run it from the main module and from submodules.

<pre><code>&lt;profile&gt;
 &lt;id&gt;root-dir&lt;/id&gt;
 &lt;activation&gt;
 &lt;file&gt;
 &lt;exists&gt;${project.basedir}/../../config/checkstyle.xml&lt;/exists&gt;
 &lt;/file&gt;
 &lt;/activation&gt;
 &lt;properties&gt;
 &lt;project.config.path&gt;${project.basedir}/../config&lt;/project.config.path&gt;
 &lt;/properties&gt;
&lt;/profile&gt;
</code></pre>

It won't work for nested modules, but I'm sure it can be modified for that using several profiles with different <code>exists</code>'s. (I have no idea why there should be "../.." in the verification tag and just ".." in the overriden property itself, but it works only in that way.)

blocks|key|1311966|text|这扩展了romaintaz的答案，这个答案很棒，因为它解决了问题，并清楚地指出了maven缺少的功能。我拿起了一个较新版本的插件，并添加了项目可能超过3层深的情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1311967|<pluginManagement>
++<plugins>
++++..
++++<plugin>
++++++<groupId>org.codehaus.gmaven</groupId>
++++++<artifactId>groovy-maven-plugin</artifactId>
++++++<version>2.0</version>
++++</plugin>
++++..
++</plugins>
</pluginManagement>|code-block|syntax|javascript|1311968|我选择不使用属性来定义文件名。注意，如果找不到build.properties，它将永远旋转。我添加了一个.git目录检测，但不想使响应过于复杂，所以这里不显示它。|1311969|++<plugin>
++++++<groupId>org.codehaus.gmaven</groupId>
++++++<artifactId>groovy-maven-plugin</artifactId>
++++++<executions>
++++++++++<execution>
++++++++++++++<phase>validate</phase>
++++++++++++++<goals>
++++++++++++++++++<goal>execute</goal>
++++++++++++++</goals>
++++++++++++++<configuration>
+++++++++++++++++<source>
++++++++++++++++++++import+java.io.File;
++++++++++++++++++++String+p+=+"build.properties";
++++++++++++++++++++while(true)+{
++++++++++++++++++++++File+f+=+new+File(p);+
++++++++++++++++++++++if(f.exists())+{
++++++++++++++++++++++++project.properties['project-properties-file']+=+f.getAbsolutePath();
++++++++++++++++++++++++break;
++++++++++++++++++++++}
++++++++++++++++++++++else+{
++++++++++++++++++++++++p+=+"../${p}";
++++++++++++++++++++++}
++++++++++++++++++++}
++++++++++++++++</source>
++++++++++++++</configuration>
++++++++++</execution>
++++++</executions>
++</plugin>|1311970|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This extends romaintaz's answer, which is awesome in that solves the problem and also clearly points out maven's missing functionality.
I picked up a later version of the plugin, and added the case where the project could be more than 3 levels deep.

<pre><code>&lt;pluginManagement&gt;
 &lt;plugins&gt;
 ..
 &lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.gmaven&lt;/groupId&gt;
 &lt;artifactId&gt;groovy-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.0&lt;/version&gt;
 &lt;/plugin&gt;
 ..
 &lt;/plugins&gt;
&lt;/pluginManagement&gt;
</code></pre>

I elected not to use a property to define the filename.
Note if the build.properties is not found this will spin forever. I added a .git dir detection, but didn't want to over complicate the response so it's not shown here.

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.gmaven&lt;/groupId&gt;
 &lt;artifactId&gt;groovy-maven-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;validate&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;execute&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;source&gt;
 import java.io.File;
 String p = "build.properties";
 while(true) {
 File f = new File(p); 
 if(f.exists()) {
 project.properties['project-properties-file'] = f.getAbsolutePath();
 break;
 }
 else {
 p = "../${p}";
 }
 }
 &lt;/source&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|1527134|text|另一种选择：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1527135|在父pom中，使用：|1527136|<properties>
+++<rootDir>${session.executionRootDirectory}</rootDir>
<properties>|code-block|syntax|javascript|1527137|在子pom中，您可以引用此变量。|1527138|主要警告:它强制您始终从主父pom目录执行命令。然后，如果您只想为某个特定模块运行命令(例如测试)，请使用以下语法：|1527139|mvn测试--项目|1527140|然后，将"path_to_test_data“变量参数化的surefire的配置可以是：|1527141|<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-surefire-plugin</artifactId>
++++<version>${surefire.plugin.version}</version>
++++<configuration>
++++++++<systemPropertyVariables>
++++++++++++<path_to_test_data>${rootDir}/../testdata</path_to_test_data>
++++++++</systemPropertyVariables>
++++</configuration>
</plugin>|1527142|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Another alternative:

in the parent pom, use:

<pre><code>&lt;properties&gt;
 &lt;rootDir&gt;${session.executionRootDirectory}&lt;/rootDir&gt;
&lt;properties&gt;
</code></pre>

In the children poms, you can reference this variable.

Main caveat: It forces you to always execute command from the main parent pom directory. Then if you want to run commands (test for example) only for some specific module, use this syntax:

mvn test --projects 

The configuration of surefire to parametize a "path_to_test_data" variable may then be:

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
 &lt;version&gt;${surefire.plugin.version}&lt;/version&gt;
 &lt;configuration&gt;
 &lt;systemPropertyVariables&gt;
 &lt;path_to_test_data&gt;${rootDir}/../testdata&lt;/path_to_test_data&gt;
 &lt;/systemPropertyVariables&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|1312072|text|我使用${basedir}..\src\访问了上面的目录|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1312073|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I accessed the dir above using ${basedir}..\src\

blocks|key|1312099|text|至少在当前的maven版本(3.6.0)中，您可以使用${maven.multiModuleProjectDirectory}|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1312100|entityMap^0|R|10|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

At least in current maven version (3.6.0) you can make use of <code>${maven.multiModuleProjectDirectory}</code>

blocks|key|1312129|text|在多项目设置中，这对我很有效|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1312130|在父pom文件中：|1312131|<properties>+<main.basedir>${project.basedir}\..</main.basedir>+</properties>|offset|length|style|CODE|1312132|在子项目中，访问这些属性，如：|1312133|${main.basedir}/|code-block|syntax|javascript|1312134|entityMap^0|0|0|0|25|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@$F|V|G|W|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|X|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|Y|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

This worked for me in the multi-project setup
In the parent pom file :
<code>&lt;properties&gt; &lt;main.basedir&gt;${project.basedir}\..&lt;/main.basedir&gt; &lt;/properties&gt;</code>
In the sub-project access these properties like:
<pre><code>${main.basedir}/
</code></pre>

I have a multi-modules project, like this one:

<pre><code>main-project/
 module1/
 module2/
 sub-module1/
 sub-module2/
 sub-module3/
 ...
 module3/
 module4/
 ...
</code></pre>

I need to define a set of properties (that are dependent of the environment on which I want to release my project) in Maven2.
I will not use <code>&lt;properties&gt;</code> as there is lots of properties...
Thus, I use the <a href="http://mojo.codehaus.org/properties-maven-plugin" rel="noreferrer">Properties Maven2 plugin</a>.

The properties files are located in the <code>main-project/</code> directory.
How can I set the correct directory in the main pom.xml, in order to specify to any children where to find the properties file?

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
 &lt;artifactId&gt;properties-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.0-alpha-1&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;initialize&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;read-project-properties&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;files&gt;
 &lt;file&gt;???/env_${env}.properties&lt;/file&gt;
 &lt;/files&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

If I set only <code>&lt;file&gt;env_${env}.properties&lt;/file&gt;</code>, then when Maven2 compiles the first module, it will not find the <code>main-project/env_dev.properties</code> file. If I set <code>&lt;file&gt;../env_${env}.properties&lt;/file&gt;</code>, then an error will be raised at the parent level, or at any sub-module level...

Maven2 property that indicates the parent directory

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个多模块的项目，就像这样：main-project/    module1/    module2/        sub-module1/        sub-module2/        sub-module3/        ...    module3/    module4/    ...我需要在M...

问指示父目录的Maven2属性
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问指示父目录的Maven2属性EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问指示父目录的Maven2属性
EN