[
https://issues.apache.org/jira/browse/YETUS-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983958#comment-14983958
]
Sean Busbey commented on YETUS-138:
-----------------------------------
+1
fine to fix on commit:
{code}
-* CHANGED\_UNFILTERED\_MODULES is a list of all modules that house all of the
CHANGED\_FILES. Be aware that the root of the source tree is reported as '.'.
-
* CHANGED\_MODULES reports which modules that appear to have source code in
them.
{code}
this description of CHANGED_MODULES is no longer accurate. needs something like
{code}
-* CHANGED\_UNFILTERED\_MODULES is a list of all modules that house all of the
CHANGED\_FILES. Be aware that the root of the source tree is reported as '.'.
-
-* CHANGED\_MODULES reports which modules that appear to have source code in
them.
+* CHANGED\_MODULES is a list of all modules that house all of the
CHANGED\_FILES. Be aware that the root of the source tree is reported as '.'.
{code}
> Skipping maven poms that don't package causes testing holes
> -----------------------------------------------------------
>
> Key: YETUS-138
> URL: https://issues.apache.org/jira/browse/YETUS-138
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Blocker
> Fix For: YETUS-83
>
> Attachments: YETUS-138.00.patch
>
>
> HADOOP-12114 impacts a pom that doesn't have a package. As a result, it gets
> dropped from CHANGED_MODULES which triggers a cascade effect. We need to
> have a better way to detect whether there is code to compile there or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
