java 代码读取pom,Maven：如何读取父POM版本

最新推荐文章于 2023-09-05 17:45:19 发布

请给我骨头

最新推荐文章于 2023-09-05 17:45:19 发布

阅读量1.5k

点赞数

文章标签： java 代码读取pom

本文讨论了在Java项目中如何避免复制粘贴重复的配置信息，通过创建一个父POM来解决这个问题。作者指出，当父POM和配置文件模块需要一起部署时，依赖版本匹配成为问题。在应用中使用父POM时，${project.version}被解析为应用版本而非父POM版本，导致找不到配置文件。解决方案是在父POM中使用${project.parent.version}或者通过pluginManagement和dependencyManagement来管理版本和配置。

摘要由CSDN通过智能技术生成

Background: Most of my Java project have a lot of boiler-plate configuration that I end up writing into my POM. (For example the sourceEncoding is always UTF-8, the organization details never change). To save having to copy-paste blocks of configuration I've created my own standard 'parent' POM I can extend for each of my projects.

I also have a number of tools that I use in every Java project I work on (e.g. checkstyle, PMD etc) so I've added the plug-ins for each tool into my standard parent pom.

PMD (and a few other tools) have an interesting problem - they requires a set of configuration files to operate correctly. Since Maven prefers to work with the concept of 'one deployable resource per module' I've created the following (simplified) structure:

|--- Config Files

\--- Parent Pom

My Template: is a maven controlled project with t