hiifong/pmd
1
0
Fork 0
forked from phoedos/pmd
Code Pull Requests Activity

[doc] Fix ruledoc for POM: ProjectVersionAsDependencyVersion

Browse Source
This commit is contained in:
Andreas Dangel 2022-10-06 17:39:56 +02:00
parent d1fa989b3c
commit 9c182974e7
No known key found for this signature in database
GPG Key ID: 93450DF2DF9A3FA3
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
pmd-xml/pom.xml
View File

@ -30,6 +30,7 @@
<delimiters> <delimiters>
<delimiter>${*}</delimiter> <delimiter>${*}</delimiter>
</delimiters> </delimiters>
<escapeString>\</escapeString>
</configuration> </configuration>
</plugin> </plugin>
</plugins> </plugins>

4
pmd-xml/src/main/resources/category/pom/errorprone.xml
View File

@ -67,7 +67,7 @@ The following types are considered valid: pom, jar, maven-plugin, ejb, war, ear,
externalInfoUrl="${pmd.website.baseurl}/pmd_rules_pom_errorprone.html#projectversionasdependencyversion"> externalInfoUrl="${pmd.website.baseurl}/pmd_rules_pom_errorprone.html#projectversionasdependencyversion">
<description> <description>
Using that expression in dependency declarations seems like a shortcut, but it can go wrong. Using that expression in dependency declarations seems like a shortcut, but it can go wrong.
By far the most common problem is the use of &#x24;{project.version} in a BOM or parent POM. By far the most common problem is the use of \${project.version} in a BOM or parent POM.
</description> </description>
<priority>3</priority> <priority>3</priority>
<properties> <properties>
@ -92,7 +92,7 @@ By far the most common problem is the use of &#x24;{project.version} in a BOM or
... ...
<dependency> <dependency>
... ...
<version>${project.version}</version> <version>\${project.version}</version>
</dependency> </dependency>
</project> </project>
]]> ]]>