[
https://issues.apache.org/jira/browse/HADOOP-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239975#comment-14239975
]
Colin Patrick McCabe commented on HADOOP-10530:
-----------------------------------------------
P.S. One way to have improved this migration would have been to have
test-patch.sh log an error message if the jdk version was 6, rather than
failing the build like maven-enforcer plugin does. This way, we would have seen
a noisy error message (but not a build failure) for everyone who had not yet
updated their precommit / postcommit / etc. job. Then after 2 or 3 weeks we
could have transitioned to maven-enforcer. hindsight is 20/20 I guess
(luckily, so is MadDog)
> Make hadoop trunk build on Java7+ only
> --------------------------------------
>
> Key: HADOOP-10530
> URL: https://issues.apache.org/jira/browse/HADOOP-10530
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.0.0, 2.6.0
> Environment: Java 1.7+
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: HADOOP-10530-001.patch, HADOOP-10530-002.patch,
> HADOOP-10530-003.patch, HADOOP-10530-004.patch, HADOOP-10530-005.patch,
> HADOOP-10530-debug.000.patch, Screen Shot 2014-09-20 at 18.09.05.png
>
>
> As discussed on hadoop-common, hadoop 3 is envisaged to be Java7+ *only*
> -this JIRA covers switching the build for this
> # maven enforcer plugin to set Java version = {{[1.7)}}
> # compiler to set language to java 1.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
