[
https://issues.apache.org/jira/browse/YETUS-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758513#comment-16758513
]
Allen Wittenauer commented on YETUS-788:
----------------------------------------
The big question is whether this is a standalone utility or just make it part
of smart-apply-patch. I'm leaning towards the latter; just provide a flag
similar or as part of --dryrun that provides two text files: 1) files patched
aka CHANGED_FILES[@] 2) module locations aka CHANGED_MODULES[@]. It's tempting
to also provide a third which is just the directories touched as a convenience
(uniq'd dirnames).
> expose patch analysis
> ---------------------
>
> Key: YETUS-788
> URL: https://issues.apache.org/jira/browse/YETUS-788
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Affects Versions: 0.9.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
>
> Expose precommit's patch analysis so that decisions can be made based upon
> what a patch touches. For example, if a change hits a certain set of
> directories or hits a certain module, some pre-work may be required prior to
> running test-patch.
> Since Yetus already has the logic to do the hard work, this should just be a
> matter of exposing the results of that work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
