You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Matt Warhaftig (JIRA)" <ji...@apache.org> on 2015/04/26 18:02:39 UTC

[jira] [Assigned] (HBASE-13344) Add enforcer rule that matches our JDK support statement

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

Matt Warhaftig reassigned HBASE-13344:
--------------------------------------

    Assignee: Matt Warhaftig

> 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
>
>
> 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)