Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 8 Oct 2014 16:06:34 +0000 (UTC)
From: "Timo Beckers (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12746699.1412769169000.218842.1412784394282@Atlassian.JIRA>
In-Reply-To: <JIRA.12746699.1412769169000@Atlassian.JIRA>
References: <JIRA.12746699.1412769169000@Atlassian.JIRA>
 <JIRA.12746699.1412769169966@arcas>
Subject: [jira] [Commented] (CASSANDRA-8083) OpenJDK 6 Dependency in dsc20
 RPM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timo Beckers commented on CASSANDRA-8083:
-----------------------------------------

Hey Michael

Thanks for the explanation, makes a lot of sense. Picking a package at random is not how Yum should handle this. On the other hand, the 'oops' case is why dependency resolution and package management exist in the first place. The landscape is definitely in a weird spot right now because OpenJDK is really taking off, along with the fact that a lot of apps are transitioning to Java7 at the same time.

As you suggested and applied in dsc21, removing the Java dependency altogether would be the perfect solution for me. The user should be in complete control over their Java stack, especially in complex environments. Cheers!

> OpenJDK 6 Dependency in dsc20 RPM
> ---------------------------------
>
>                 Key: CASSANDRA-8083
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8083
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>         Environment: Packages pulled from the community repo at http://rpm.datastax.com/community as per the installation guidelines.
>            Reporter: Timo Beckers
>            Assignee: Michael Shuler
>            Priority: Minor
>             Fix For: 2.0.10
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> According to https://issues.apache.org/jira/browse/CASSANDRA-6925 and https://issues.apache.org/jira/browse/CASSANDRA-7243, the Cassandra project only produces platform-agnostic .tar.gz. The person in the second ticket was referred to https://support.datastax.com/home to report RPM issues, but this ticketing system requires a login to post and registration is not open. I realize this is not the right issue tracker to post this on, but I hope to reach the community repo maintainer through this one.
> The problem I'm facing only seems to occur for the 'cassandra20' package from the Datastax community repo. On a fresh CentOS installation with no prior Java stack installed:
> # yum install dsc20
> Installing:
>  dsc20
> Installing for dependencies:
>  java-1.6.0-openjdk
> ...
>  cassandra20
> This inevitably results in the following log message:
> "Cassandra 2.0 and later require Java 7 or later."
> and sometimes
> "Unsupported major.minor version 51.0"
> The issue seems to be with the 'cassandra20' package that depends on openjdk6. I noticed the same behaviour with dsc21 a couple weeks ago, but this seems to be fixed already. Could you please take a look or assign this to a person who could?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)