hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14809) hadoop-aws shell profile not being built
Date Tue, 29 Aug 2017 21:22:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Loughran updated HADOOP-14809:
    Attachment: HADOOP-14809-HADOOP-13345-002.patch

Steve's patch

comments out the 2nd entry in hadoop-aws/pom.xml and adds a test in hadoop-dist which scans
the shellscript dir of the final output for all the listed entries being present. it's only
kicking off in mvn verify; I think mvn-test is probably better, though I need to understand
more when the packaging is being created. Key point: we can have yetus makes sure that the
XML profiles we expect are being created. Indeed, with a second <condition> we can verify
that only those we expect are created, forcing an update to the pom.xml and list of scripts
to test for whenever a new one goes in

> hadoop-aws shell profile not being built
> ----------------------------------------
>                 Key: HADOOP-14809
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14809
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: HADOOP-13345
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Blocker
>         Attachments: HADOOP-14809.00.patch, HADOOP-14809-HADOOP-13345-002.patch, HADOOP-14809.HADOOP-13345.00.patch
> As discussed on hadoop common list; the creation of the s3guard shell profile is stopping
the hadoop-aws profile being created, so you can't set up the CP properly there

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message