[ https://issues.apache.org/jira/browse/HBASE-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581508#comment-14581508 ]
Sean Busbey commented on HBASE-13344: ------------------------------------- We could try to chase down why -source and -target arguments on the maven compiler plugin don't appear to be working for us. The docs for both 1.7 and 1.8 claim that javac will produce correct bytecode when given the args. > 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, 0.94.28, 0.98.13, 1.0.2, 1.2.0, 1.1.1 > > 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)