Tests never exercise @{baseVersion}@ used in DEFAULT constants

Open Beginner friendly
#64 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java

Research direction

Start by reading MappingUtils.java around lines 72 and 78, then inspect MappingUtilsTest.java and run its existing tests. Add a focused test that evaluates an expression containing @{baseVersion}@ and confirms it resolves as expected; done means the test passes and covers the previously untested default mapping behavior.

Written by the indexing model from the issue text.

Description

Description

Both DEFAULT_FILE_NAME_MAPPING and DEFAULT_FILE_NAME_MAPPING_CLASSIFIER use @{baseVersion}@ in their expressions (MappingUtils.java:72,78). However, every test in MappingUtilsTest.java uses @{version}@ in its expressions instead.

Risk

There is no test coverage verifying that @{baseVersion}@ resolves correctly, or documenting the behavioral difference between baseVersion and version.

Suggestion

Add at least one test that evaluates a mapping expression containing @{baseVersion}@ to ensure it resolves as expected.

Dominant language
Java
Stars
2
Forks
7
Avg merge
3h 47m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/maven-mapping

All issues in apache/maven-mapping

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.