issueManagement/system not used by changes:changes, must override
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
Research direction
Start with the changes.xml report generation and the action definition in changes.mdo, then reproduce the issue in commons-validator with mvn clean verify site -DskipTests. Trace how the inherited POM /issueManagement/system value is handled for changes actions; done means the generated changes.html uses the configured JIRA key rather than the default URL.
Written by the indexing model from the issue text.
Description
Affected version
3.0.0-M3
Bug description
When generating a site, the generating a page for changes.xml does NOT use the POM's /issueManagement/system value to select, for example "JIRA" and instead uses the "defauit", which generates broken URLs on that page.
For example:
git clone https://github.com/apache/commons-validator.git
cd commons-validator
git checkout 4c9a0660a0d29bc7e9891f24be86f9539f42e419
mvn clean verify site -DskipTests
open target/site/changes.html#a1.10.1
Youi'll see the link to VALIDATOR-502 with the href https://issues.apache.org/jira/browse/ViewIssue.jspa?key=VALIDATOR-502 which uses the "default" key instead of the "JIRA" key defined in /issueManagement/system
Note that /issueManagement/system is inherited from the parent POM, which works since the JIRA report is OK; it's the changes.xml report that's broken.
I see in changes.mdo that an action supports a system attribute. Shouldn't that inherit /issueManagement/system? Otherwise, you need to specify system on each action, which seems redundant.
- Dominant language
- Java
- Stars
- 15
- Forks
- 22
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 7
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.
More from apache/maven-changes-plugin
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/maven-changes-plugin#650 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 52/100
apache/maven-changes-plugin#633 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/maven-changes-plugin#610 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
apache/maven-changes-plugin#608 ·
-
NullPointerException: Cannot invoke "java.lang.CharSequence.toString()" because "target" is null Openbug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
apache/maven-changes-plugin#130 · 1 comment ·
All issues in apache/maven-changes-plugin
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100