在log4j.properties中使用maven的properites变量

最新推荐文章于 2023-10-17 12:39:52 发布

原创最新推荐文章于 2023-10-17 12:39:52 发布 · 686 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#java #开发工具

J2EE 专栏收录该内容

11 篇文章

订阅专栏

本文介绍如何在Maven项目中使用资源过滤功能来替换log4j配置文件中的变量，包括Maven属性如${project.artifactId}

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

详情请参考

http://stackoverflow.com/questions/3265250/can-i-substitute-eclipse-and-maven-variables-into-a-log4j-properties-file

http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html

http://www.coderanch.com/t/107838/tools/variable-substitution-log-properties-file

Can I substitute Eclipse and Maven variables into a log4j.properties file?

up vote 4 down vote favorite

You can use system properties in log4j configuration files using a ${variablename} syntax.

Can you include Eclipse variables (like the project name) and Maven variables (like the artifact ID) in there too, and have them substituted during the respective build?

edited Jul 17 '10 at 2:06

Pascal Thivent
320k 46 637 864

asked Jul 16 '10 at 13:24

Brabster
20.1k 12 82 144

add a comment

1 Answer

active oldest votes

up vote 5 down vote accepted

Can you include Eclipse variables (like the project name) and Maven variables (like the artifact ID) in there too, and have them substituted during the respective build?

For the later (Maven variables), you can use resources filtering. Activate it by adding a <filtering>element to your POM and setting it to true:

<project>
  ...
  <build>
    ...
    <resources><resource><directory>src/main/resources</directory><filtering>true</filtering></resource>
      ...
    </resources>
    ...
  </build>
  ...
</project>

And any Maven property like ${project.artifactId} used in a resource file will now get replaced by its value. You can define includes/excludes for finer control of resources that you want to filter. Refer to the above link for examples.

For the former (Eclipse variables), Maven is not aware of them so, obviously, this solution won't work and I actually suggest sticking to Maven filtering (the Maven build should be the reference).

If you are using m2eclipse, this will work transparently inside Eclipse.