Adjust bisect scripts and OpenCommunityBuild to use new nightlies repository

[WojciechMazur]

Related to #23761
When we'll switch nightlies to be published in the new repository instead on on central.sonatype.org we need to adjust the related scripts:

Bisecting tool

Bisect tool uses maven metadata.xml to gather information about available versions, it would need to be merged with version obtained from new repo metadata.xml
Also the scala runner executing the snippet would need to be adjusted to use new repository

Open Community Build

It also fetches avaialbe versions using metadata.xml, the code to find latest versions would need to be adjusted

Documentation

https://docs.scala-lang.org/overviews/core/nightlies.html needs to be updated (scala/docs.scala-lang#3206)

[hamzaremmal]

Bisect tool uses maven metadata.xml to gather information about available versions, it would need to be merged with version obtained from new repo metadata.xml
Also the scala runner executing the snippet would need to be adjusted to use new repository

This might be trivial as I configured an instance of a repository that mixes and gives a unique view containing Maven Central artifacts (for previous Scala 3 nightlies), the local storage of the new repository and the Scala 2 nightlies. Hence, every nightly of Scala 2 and 3 should be accessible from that repository.
@WojciechMazur I've sent you the link to view it

[hamzaremmal]

Other tasks I've kept in mind related to the nightly changes:

• Add the resolver in sbt
• Update scala-cli to use this resolver when referring to 3.nightly (Support fetching Scala 3 nightlies from new repository VirtusLab/scala-cli#3836)
• Write a blog post about this change

[WojciechMazur]

I can see that infra was adjusted and moved to new scala-lang.org domain, however, I can see that it requires authorization, in such case current scripts would not work. Probably also it would be hard to make it use from scala-cli or other build tools.

> curl https://repo.scala-lang.org/artifactory/maven-nightlies/org/scala-lang/scala3-compiler_3/maven-metadata.xml
{
  "errors" : [ {
    "status" : 401,
    "message" : "Authentication is required"
  } ]
}%                                        

[hamzaremmal]

I can see that infra was adjusted and moved to new scala-lang.org domain, however, I can see that it requires authorization, in such case current scripts would not work. Probably also it would be hard to make it use from scala-cli or other build tools.

curl https://repo.scala-lang.org/artifactory/maven-nightlies/org/scala-lang/scala3-compiler_3/maven-metadata.xml
{
"errors" : [ {
"status" : 401,
"message" : "Authentication is required"
} ]
}%

I haven't yet configured the instance. This is the actual production one, not the staging I prepared Friday night.
I merged your PR as I needed to merge something in main to verify some caching properties on a call with @Duhemm.
I will let you know when it is ready.

[hamzaremmal]

@WojciechMazur should be good now, can you try?

[WojciechMazur]

@WojciechMazur should be good now, can you try?

Previously it redirected to login page, now there is a sign-in pop-up in the browser. Would still require authentication

[hamzaremmal]

@WojciechMazur should be good now, can you try?

Previously it redirected to login page, now there is a sign-in pop-up in the browser. Would still require authentication

I will let you know when I configure it, I need to finish a poster for a conference at the moment because I need to send it for printing ASAP.

[hamzaremmal]

@WojciechMazur Just confirmed everything is working by using the nightly is a fresh sbt project. Can you please confirm it works for what you intend to do with it?