[MCHECKSTYLE-431] Avoid creating unnecessary target files for pom projects
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
Research direction
Start by reproducing the Maven configuration and output for a pom project, then trace where target/checkstyle-cachefile, target/checkstyle-checker.xml, target/checkstyle-result.xml, and target/checkstyle-suppressions.xml are generated. Done means a pom project without Java code no longer creates these files while the check goal still runs successfully.
Written by the indexing model from the issue text.
Description
Alexis Jehan opened MCHECKSTYLE-431 and commented
Because pom projects do not have Java code, It is not necessary to create "target/checkstyle-cachefile", "target/checkstyle-checker.xml", "target/checkstyle-result.xml" and "target/checkstyle-suppressions.xml" files for these projects.
Maven configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>3.2.1</version>
<dependencies>
<dependency>
<groupId>com.puppycrawl.tools</groupId>
<artifactId>checkstyle</artifactId>
<version>10.9.3</version>
</dependency>
</dependencies>
<configuration>
<configLocation>checkstyle.xml</configLocation>
<suppressionsLocation>checkstyle-suppressions.xml</suppressionsLocation>
<includeTestSourceDirectory>true</includeTestSourceDirectory>
<violationSeverity>info</violationSeverity>
</configuration>
<executions>
<execution>
<id>checkstyle-check</id>
<phase>validate</phase>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
Maven output:
[INFO] --- checkstyle:3.2.1:check (checkstyle-check) @ parent-project ---
[INFO] You have 0 Checkstyle violations.
Content of the generated "target/checkstyle-result.xml":
<?xml version="1.0" encoding="UTF-8"?>
<checkstyle version="10.9.3">
</checkstyle>
Affects: 3.2.1
- Dominant language
- Java
- Stars
- 98
- Forks
- 69
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/maven-checkstyle-plugin
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
Update dependencies.May be free again A pull request for this issue was closed without being merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
DefaultCheckstyleExecutor should be a failure, not an errorPossibly taken @efegokdemir claimed this 36 days ago. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
apache/maven-checkstyle-plugin#656 · 1 comment ·
-
Add ability to print warnings when `failOnViolation: true` and `violationSeverity: error`Possibly taken @efegokdemir claimed this 35 days ago. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 50/100
apache/maven-checkstyle-plugin#648 · 5 comments ·
All issues in apache/maven-checkstyle-plugin
Similar issues
-
pending:code-area pending:issue-category to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area:core bug priority:p2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aomarai/minecraft-mcp#247 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
antonyrag/ragleap-core#1062 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
projectnessie/nessie#13256 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Vakore/ZappierGames#232 ·