[
https://issues.apache.org/jira/browse/MCHANGES-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MCHANGES-412.
--------------------------------------------
Resolution: Won't Do
Closing as too idiosyncratic. I don't think there's enough interest in this to
justify the extra weight and maintenance burden.
> Allow an action to carry an optional scope
> ------------------------------------------
>
> Key: MCHANGES-412
> URL: https://issues.apache.org/jira/browse/MCHANGES-412
> Project: Maven Changes Plugin
> Issue Type: New Feature
> Components: changes.xml
> Reporter: Gary D. Gregory
> Priority: Major
>
> 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?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
