[
https://issues.apache.org/jira/browse/YETUS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997291#comment-14997291
]
Allen Wittenauer commented on YETUS-172:
----------------------------------------
Unmatched profile activations aren't failures for maven. You can see these in
trunk all the time for native. The build failed because of:
{code}
[ERROR] Plugin org.apache.hadoop:hadoop-maven-plugins:2.8.0-SNAPSHOT or one of
its dependencies could not be resolved: Failed to read artifact descriptor for
org.apache.hadoop:hadoop-maven-plugins:jar:2.8.0-SNAPSHOT: Could not find
artifact org.apache.hadoop:hadoop-maven-plugins:pom:2.8.0-SNAPSHOT -> [Help 1]
{code}
> Hadoop pre-commit with shell script patches fails on branch-2, because
> shelltest Maven profile does not exist.
> --------------------------------------------------------------------------------------------------------------
>
> Key: YETUS-172
> URL: https://issues.apache.org/jira/browse/YETUS-172
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Reporter: Chris Nauroth
>
> When Yetus runs a pre-commit patch on Hadoop, and it detects changes in Bash
> code, it activates the {{shelltest}} Maven profile for the build to run BATS
> tests. This profile exists in Hadoop trunk, but not branch-2. For a
> branch-2 patch on bash scripts, this will cause the pre-commit to fail. This
> issue tracks enhancing the Hadoop personality to skip the {{shelltest}}
> profile on branches that do not support the profile.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
