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

Stefan Miklosovic commented on CASSANDRA-18049:
-----------------------------------------------

I am not sure how much of an issue is this but I see this in logs doing ant jar:

{code}
resolver-dist-lib:
[resolver:resolve] Downloading 
https://nexus.chronicle.software/content/repositories/thirdparty/net/openhft/third-party-bom/3.22.4-SNAPSHOT/maven-metadata.xml
[resolver:resolve] Downloading 
https://nexus.chronicle.software/content/repositories/snapshots/net/openhft/third-party-bom/3.22.4-SNAPSHOT/maven-metadata.xml
[resolver:resolve] Downloading 
https://nexus.chronicle.software/content/repositories/releases/net/openhft/third-party-bom/3.22.4-SNAPSHOT/maven-metadata.xml
[resolver:resolve] Could not transfer metadata 
net.openhft:third-party-bom:3.22.4-SNAPSHOT/maven-metadata.xml from/to 
third-party-release 
(https://nexus.chronicle.software/content/repositories/thirdparty/): status 
code: 401, reason phrase: Unauthorized (401)
[resolver:resolve] Could not transfer metadata 
net.openhft:third-party-bom:3.22.4-SNAPSHOT/maven-metadata.xml from/to 
chronicle-enterprise-snapshots 
(https://nexus.chronicle.software/content/repositories/snapshots): status code: 
401, reason phrase: Unauthorized (401)
[resolver:resolve] Could not transfer metadata 
net.openhft:third-party-bom:3.22.4-SNAPSHOT/maven-metadata.xml from/to 
chronicle-enterprise-release 
(https://nexus.chronicle.software/content/repositories/releases): status code: 
401, reason phrase: Unauthorized (401)

{code}

> Update Chronicle Queue
> ----------------------
>
>                 Key: CASSANDRA-18049
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18049
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Ekaterina Dimitrova
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 5.0
>
>
> According to [this|https://chronicle.software/chronicle-support-java-17] 
> article:
> {code:java}
> Starting from chronicle-bom-2.22ea26, all new releases can be run under Java 
> 17 when run on the class path (but not yet under the module path).{code}
> This BOM is newer than what we currently have in both 4.1 and trunk. 4.1 
> points in comments to 
> [https://mvnrepository.com/artifact/net.openhft/chronicle-bom/1.16.23] which 
> I believe was just forgotten to be updated/removed. The versions we see 
> correspond to this BOM 
> [https://mvnrepository.com/artifact/net.openhft/chronicle-bom/2.20.226]
> It is still older than chronicle-bom-2.22ea26 so we need to upgrade. I 
> suggest we also add a comment again which BOM is considered, this makes 
> things easier.
> Further to running CI, review of the CHANGE logs needs to happen to ensure we 
> do not miss anything that can impact us and it is not caught by our tests.
> For testing with JDK17, please, contact [~e.dimitrova] for latest branch and 
> CI config (at this point feature branch in the cassandra repo does not exist)
>  



--
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

Reply via email to