hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13344) Add enforcer rule that matches our JDK support statement
Date Thu, 14 May 2015 23:16:00 GMT

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

Sean Busbey commented on HBASE-13344:
-------------------------------------

I *think* so. This rule only validates byte code versions in class files, so once things are
built with the given compileSource version it doesn't care what version JVM is used to run
the tests.

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

Mime
View raw message