[
https://issues.apache.org/jira/browse/BIGTOP-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911049#comment-13911049
]
Konstantin Boudnik commented on BIGTOP-1218:
--------------------------------------------
bq. If you call installing JDK7 forcing, then sure we are forcing and the
refactoring is not going to change that forcing
Actually it will do the forcing, because once the current BIGTOP-1218 is
committed there's no option of not installing JDK7. With my proposal I can at
least avoid it by not running this special new jdk7 manifest. While I feel for
Hive community, my foremost interest is to make sure that one group of users is
forced in doing something that another group of users needs. Thus my request to
preserve the semantics as much as possible.
Now, if you use the curl trick to download jdk7 bits you won't be needing too
deep knowledge of puppet nor fixing non-idempotent repo-insert operation. The
whole modification will be quite non-intrusive and won't change much in the
existing recipes. Am I making sense?
> 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)
