[MNGSITE-494] Clarify how to modify inheritance with attributes prefixed with "combine."
- Dominant language
- Java
- Stars
- 123
- Forks
- 301
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 32
Description
**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** opened **[MNGSITE-494](https://issues.apache.org/jira/browse/MNGSITE-494?redirect=false)** and commented
The merging options used for inheritance are only partially described within https://maven.apache.org/pom.html#advanced_configuration_inheritance but in fact apply everywhere (not only to plugin configuration). Also the attributes `combine.id` and `combine.keys` used in https://github.com/codehaus-plexus/plexus-utils/blob/7f5114af7d0c4d19838a9e0082758ec0f5e0269e/src/main/java/org/codehaus/plexus/util/xml/Xpp3DomUtils.java#L124 are not described at all.
---
No further details from [MNGSITE-494](https://issues.apache.org/jira/browse/MNGSITE-494?redirect=false)
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the advanced_configuration_inheritance section at https://maven.apache.org/pom.html#advanced_configuration_inheritance and compare it with the inheritance behavior referenced in plexus-utils' Xpp3DomUtils.java. Document that the merging options apply beyond plugin configuration, and explain the combine.id and combine.keys attributes. Done means the relevant inheritance rules and both attributes are described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100