Provide an easier way to update the used PMD version
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 99
- Forks
- 42
- Avg merge
- 20h 19m
- Merged PRs (30d)
- 19
Description
Update the integrated PMD version to xxx.
Ideally, PMD itself would be available in a p2-repository, which the eclipse plugin can then just reference. Given, that the API didn't change, it should be simple then, to update PMD and keep the plugin.
This will however require a bigger change in the plugin and also make sure, that each PMD version is also released into a p2 repository during release.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing how the Eclipse plugin currently integrates and updates its PMD version, then read PMD issue 1177 for the proposed p2-repository approach. Trace the plugin release process and determine what must change so each PMD version is published to and referenced from a p2 repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100