eclipse-xtext / eclipse-xtext/xtext
[mvn] Use ${project.version} instead of hard-coded references
Open
Nobody has claimed this yet.
releng
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
Some POMs contain redundant information on the used Xtext version, e.g. xtext-core/releng/pom.xml
<dependency>
<groupId>org.eclipse.xtext</groupId>
<artifactId>org.eclipse.xtext</artifactId>
<version>2.15.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.eclipse.xtext</groupId>
<artifactId>org.eclipse.xtext</artifactId>
<version>2.15.0-SNAPSHOT</version>
<classifier>sources</classifier>
</dependency>
The version 2.15.0-SNAPSHOT can be replaced by ${project.version}.
This makes the changeset smaller when changing versions.
Contributor 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.
Research direction
Start with xtext-core/releng/pom.xml and search the other POMs for hard-coded Xtext versions such as 2.15.0-SNAPSHOT. Replace redundant version references with ${project.version}, then verify that all relevant POMs use the project version and that the resulting changeset contains only those updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100