[jira] [Commented] (CASSANDRA-18817) RPM install does not work with jdk17

2023-09-04 Thread Claude Warren (Jira)


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

Claude Warren commented on CASSANDRA-18817:
---

My change is for  CASSANDRA-17773 where I propose extracting the common 
"boilerplate" code to simplify writing files that start/stop Cassandra and its 
stand-alone tools.  I don't think that it would impact this issue in any way. 

The changes just centralize the code to discover where the cassandra.in.sh file 
is, it does not change the contents of the file.

> RPM install does not work with jdk17
> 
>
> Key: CASSANDRA-18817
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18817
> Project: Cassandra
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 5.0-alpha
>
>
> The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the 
> corresponding redhat/cassandra.in.sh was not.
> This means when cassandra starts on a rpm install using jdk17 the 
> jvm11-server.options file is still used. And so it fails.
> Initial patch that works: 
> https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0
>  
> Maybe it is possible to find a superior solution, like wrapping this file 
> instead of duplicating it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-18817) RPM install does not work with jdk17

2023-09-03 Thread Brandon Williams (Jira)


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

Brandon Williams commented on CASSANDRA-18817:
--

+1

> RPM install does not work with jdk17
> 
>
> Key: CASSANDRA-18817
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18817
> Project: Cassandra
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 5.0-alpha
>
>
> The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the 
> corresponding redhat/cassandra.in.sh was not.
> This means when cassandra starts on a rpm install using jdk17 the 
> jvm11-server.options file is still used. And so it fails.
> Initial patch that works: 
> https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0
>  
> Maybe it is possible to find a superior solution, like wrapping this file 
> instead of duplicating it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-18817) RPM install does not work with jdk17

2023-09-03 Thread Michael Semb Wever (Jira)


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

Michael Semb Wever commented on CASSANDRA-18817:


[~claude], fyi, touches on some of the work you were trying to do with our 
script configs.

> RPM install does not work with jdk17
> 
>
> Key: CASSANDRA-18817
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18817
> Project: Cassandra
>  Issue Type: Bug
>  Components: Packaging
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 5.0-alpha
>
>
> The cassandra.in.sh file was updated as part of CASSANDRA-18255 but the 
> corresponding redhat/cassandra.in.sh was not.
> This means when cassandra starts on a rpm install using jdk17 the 
> jvm11-server.options file is still used. And so it fails.
> Initial patch that works: 
> https://github.com/apache/cassandra/compare/cassandra-5.0...thelastpickle:cassandra:mck/redhat-jdk17-fix/5.0
>  
> Maybe it is possible to find a superior solution, like wrapping this file 
> instead of duplicating it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org