[
https://issues.apache.org/jira/browse/BIGTOP-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910934#comment-13910934
]
Konstantin Boudnik commented on BIGTOP-1218:
--------------------------------------------
bq. Therefore, it's ok to do refactoring in a follow-up JIRA in my opinion
This seems like a bit of inverse logic to me, Mark. First, we introduce the
behavior they forces JDK7 installation; then we split it and say - ok, now you
can have your old way of being able to just have JDK6. Splitting the package
doesn't seems like a lot of work - perhaps we'd better do it at once? Unless,
there's something else standing in the path.
> Add JDK7 to Bigtop toolchain
> ----------------------------
>
> Key: BIGTOP-1218
> URL: https://issues.apache.org/jira/browse/BIGTOP-1218
> Project: Bigtop
> Issue Type: Bug
> Components: Build
> Affects Versions: 0.8.0
> Reporter: Mark Grover
> Assignee: Mark Grover
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1218.1.patch, BIGTOP-1218.2.patch
>
>
> Brock Noland filed a request for adding JDK7 to Bigtop toolchain so they can
> use it in their Hive pre-commit/integration test jobs. This JIRA will track
> that effort.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
