[jira] [Commented] (CASSANDRA-15245) cassandra-all| library uses non-existent Guava classes
[
https://issues.apache.org/jira/browse/CASSANDRA-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892907#comment-16892907
]
Abhijit Sarkar commented on CASSANDRA-15245:
[~cnlwsu] Filed task https://issues.apache.org/jira/browse/CASSANDRA-15248
> cassandra-all| library uses non-existent Guava classes
> --
>
> Key: CASSANDRA-15245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15245
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> The
> [cassandra-all|https://search.maven.org/artifact/org.apache.cassandra/cassandra-all/3.11.4/jar]
> library references classes that have been removed from Guava, for example
> {{com.google.common.base.CharMatcher.DIGIT}}. This causes runtime errors like
> {code}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.cassandra.io.sstable.format.SSTableFormat$Type
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15245) cassandra-all| library uses non-existent Guava classes
[
https://issues.apache.org/jira/browse/CASSANDRA-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892859#comment-16892859
]
Chris Lohfink commented on CASSANDRA-15245:
---
I think updating guava on trunk makes sense, should be pretty straight forward
patch. Perhaps change title of Jira or open a new one as the
{{NoClassDefFoundError}} is just a dependency conflict from putting projects
requiring different versions of guava in classpath. {{cassandra-all}} isnt
really a client library and has no shading available for netty/guava/commons
etc so importing it into your project will likely have many conflicts.
> cassandra-all| library uses non-existent Guava classes
> --
>
> Key: CASSANDRA-15245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15245
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> The
> [cassandra-all|https://search.maven.org/artifact/org.apache.cassandra/cassandra-all/3.11.4/jar]
> library references classes that have been removed from Guava, for example
> {{com.google.common.base.CharMatcher.DIGIT}}. This causes runtime errors like
> {code}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.cassandra.io.sstable.format.SSTableFormat$Type
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15245) cassandra-all| library uses non-existent Guava classes
[
https://issues.apache.org/jira/browse/CASSANDRA-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892539#comment-16892539
]
Abhijit Sarkar commented on CASSANDRA-15245:
[~zznate] Guava v23.3-jre in master does remove {{DIGIT}} but as far as
compatibility with latest code is concerned, is almost 2 years old. Latest is
28.0-jre.
I'm not sure about your comment about upgrading within a stable major release;
as long as no API is changed, there's nothing in [SEMVER|https://semver.org]
that says transitive dependencies would have to be frozen.
> cassandra-all| library uses non-existent Guava classes
> --
>
> Key: CASSANDRA-15245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15245
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> The
> [cassandra-all|https://search.maven.org/artifact/org.apache.cassandra/cassandra-all/3.11.4/jar]
> library references classes that have been removed from Guava, for example
> {{com.google.common.base.CharMatcher.DIGIT}}. This causes runtime errors like
> {code}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.cassandra.io.sstable.format.SSTableFormat$Type
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15245) cassandra-all| library uses non-existent Guava classes
[
https://issues.apache.org/jira/browse/CASSANDRA-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892387#comment-16892387
]
Nate McCall commented on CASSANDRA-15245:
-
Hi [~sarkara1] thank you for the clarification. I read this issue initially as
a dependency problem when importing cassandra-all.jar. Apologies for the
confusion.
We do update dependencies such as guava on occasion (CASSANDRA-9653,
CASSANDRA-6639), but doing so within a stable major release without a
compelling reason such as a security issue or critical bug is generally not
something we do.
Do note that trunk is running a newer version:
https://github.com/apache/cassandra/blob/trunk/build.xml#L490
> cassandra-all| library uses non-existent Guava classes
> --
>
> Key: CASSANDRA-15245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15245
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> The
> [cassandra-all|https://search.maven.org/artifact/org.apache.cassandra/cassandra-all/3.11.4/jar]
> library references classes that have been removed from Guava, for example
> {{com.google.common.base.CharMatcher.DIGIT}}. This causes runtime errors like
> {code}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.cassandra.io.sstable.format.SSTableFormat$Type
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15245) cassandra-all| library uses non-existent Guava classes
[
https://issues.apache.org/jira/browse/CASSANDRA-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892311#comment-16892311
]
Abhijit Sarkar commented on CASSANDRA-15245:
[~zznate] I think you completely missed the point of this ticket. DIGIT is not
present in the latest Guava. You are using version 18, which is very old, and
this ticket is for you to upgrade to the latest or close. What you’re asking is
the rest of the world to stick to a deprecated library just because you’re.
Please reopen this ticket as it’s a valid problem.
> cassandra-all| library uses non-existent Guava classes
> --
>
> Key: CASSANDRA-15245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15245
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> The
> [cassandra-all|https://search.maven.org/artifact/org.apache.cassandra/cassandra-all/3.11.4/jar]
> library references classes that have been removed from Guava, for example
> {{com.google.common.base.CharMatcher.DIGIT}}. This causes runtime errors like
> {code}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.cassandra.io.sstable.format.SSTableFormat$Type
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
