[
https://issues.apache.org/jira/browse/HBASE-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567584#comment-14567584
]
Hudson commented on HBASE-13344:
--------------------------------
FAILURE: Integrated in HBase-1.1 #515 (See
[https://builds.apache.org/job/HBase-1.1/515/])
HBASE-13344 - Add max Java version check for pom dependencies. (busbey: rev
0a46edb563d37a0e865f0572d828d79b75b86691)
* pom.xml
HBASE-13344 Addendum - Move max Java version check to release. (busbey: rev
056caf0a2a130b9749f10a70be9a040623e68b71)
* pom.xml
> Add enforcer rule that matches our JDK support statement
> --------------------------------------------------------
>
> Key: HBASE-13344
> URL: https://issues.apache.org/jira/browse/HBASE-13344
> Project: HBase
> Issue Type: Improvement
> Components: build
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Assignee: Matt Warhaftig
> Priority: Minor
> Labels: beginner, maven
> Fix For: 2.0.0
>
> Attachments: HBASE-13344-master.patch,
> HBASE-13344-master_addendum_v1.patch, HBASE-13344-master_v2.patch
>
>
> The [ref guide gives a list of JDKs that we expect our hbase versions to work
> with at runtime|http://hbase.apache.org/book.html#basic.prerequisites].
> Let's add in the extra-enforcer-rules mojo and start using [the bytecode
> version
> rule|http://mojo.codehaus.org/extra-enforcer-rules/enforceBytecodeVersion.html]
> to make sure that the result of our builds on a given branch won't fail out
> because of a misconfigured target jdk version (or a dependency that targets a
> later jdk).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
