[MCHANGES-412] Allow an action to carry an optional scope
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system
Research direction
Start with the changes.xml action examples and trace how action attributes are represented and consumed in the plugin. Define the optional scope behavior and its accepted values, then verify that scoped actions are accepted and their scope is visible to users without breaking actions that omit it.
Written by the indexing model from the issue text.
Description
Gary D. Gregory opened MCHANGES-412 and commented
In changes.xml, I would like an action to carry an optional {}scope{}.
This would help users understand what changes affect which part of their projects.
For example:
<action issue="ABC-189" type="fix" {}scope="runtime"{}>Fix some bug</action>
<action issue="ABC-190" type="update" {}scope="test"{}>Bump dependency foo from 1 to 2</action>
<action issue="ABC-191" type="update" {}scope="build"{}>Bump commons-parent foo from 1 to 2</action>
<action issue="ABC-191" type="update" {}scope="site"{}>Documented this and that</action>
The use of the scope documents where the change applies, usually runtime, test, or build, but it could be string maybe.
This somewhat parallels the concept of a scope in a dependency so the value set could be the same as allowed for a dependency scope but that might be too restrictive.
Thoughts?
No further details from MCHANGES-412
- 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 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
apache/maven-changes-plugin#619 ·
-
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 ·
All issues in apache/maven-changes-plugin
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
inu-appcenter/memorIN-backend#288 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
frontend maui-pilot pilot-ask question
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area/plugin
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kestra-io/plugin-kestra#190 ·