Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Thu, 26 Mar 2015 20:06:52 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12785997.1427400364000.41132.1427400412931@Atlassian.JIRA>
In-Reply-To: <JIRA.12785997.1427400364000@Atlassian.JIRA>
References: <JIRA.12785997.1427400364000@Atlassian.JIRA>
 <JIRA.12785997.1427400364796@arcas>
Subject: [jira] [Created] (HBASE-13344) Add enforcer rule that matches our
 JDK support statement
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sean Busbey created HBASE-13344:
-----------------------------------

             Summary: 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
            Reporter: Sean Busbey
            Priority: Minor
             Fix For: 2.0.0


The [ref guide gives a list of JDKs that we expect our hbase versions to work with at runtime|].

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)