[ 
https://issues.apache.org/jira/browse/HADOOP-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087649#comment-16087649
 ] 

Rushabh S Shah commented on HADOOP-14474:
-----------------------------------------

{quote}
To match it with a single digit version number, it should be 
HADOOP-14521-branch-2.8-2.patch
Note the dash vs. period in the last chunk. You can see an example why periods 
tend to be confusing here: 
{quote}
Then maybe we should change the wiki on "How to contribute" to be more clear.
https://wiki.apache.org/hadoop/HowToContribute
{noformat}
Naming your patch

Patches for trunk should be named according to the Jira, with a version number: 
<jiraName>.<versionNum>.patch, e.g. HADOOP-1234.001.patch, HDFS-4321.002.patch.

Patches for a non-trunk branch should be named 
<jiraName>-<branchName>.<versionNum>.patch, e.g. HDFS-1234-branch-2.003.patch. 
The branch name suffix should be the exact name of a git branch, such as 
"branch-2". Jenkins will check the name of the patch and detect the appropriate 
branch for testing.
{noformat}


> Use OpenJDK 7 instead of Oracle JDK 7 to avoid oracle-java7-installer failures
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-14474
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14474
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 2.8.0, 2.7.3
>            Reporter: Akira Ajisaka
>            Assignee: Akira Ajisaka
>             Fix For: 2.9.0, 2.7.4, 2.6.6, 2.8.2
>
>         Attachments: HADOOP-14474-branch-2.01.patch
>
>
> Recently Oracle has changed the download link for Oracle JDK7, and that's why 
> oracle-java7-installer fails. Precommit jobs for branch-2* are failing 
> because of this failure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to