hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13344) Add enforcer rule that matches our JDK support statement
Date Mon, 01 Jun 2015 16:54:18 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567566#comment-14567566

Hudson commented on HBASE-13344:

FAILURE: Integrated in HBase-1.0 #940 (See [https://builds.apache.org/job/HBase-1.0/940/])
HBASE-13344 - Add max Java version check for pom dependencies. (busbey: rev 833f56f9ed34fe35123e86ae828e4fd46b89a0fc)
* pom.xml
HBASE-13344 Addendum - Move max Java version check to release. (busbey: rev dadd824ddcf02a2deb3d6f84ef48e7aef6aaf4ca)
* 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,
> The [ref guide gives a list of JDKs that we expect our hbase versions to work with at
> 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

View raw message