Hi James & James,
I agree we should move to repo.gradle.org/gradle/libs-releases, for all the
technical reasons you've provided, but also to make Grails more future
proof and communicate it as more "integrated" with relevant technologies
(if that makes any sense, it does in my mind).
Gianluca Sar
I think we should keep using repo.grails.org for now (below the other
repos, in the repositories block), and await JFrogs answer, if we can keep
using it.
/Mattias
Den lör 3 maj 2025 kl 10:42 skrev Gianluca Sartori :
> Hi James & James,
>
> I agree we should move to repo.gradle.org/gradle/libs-r
@Mattias, what are your thoughts about creating a new repository on
repo.grails.org to isolate legacy artifacts?
On Sat, May 3, 2025 at 7:52 AM Mattias Reichel
wrote:
> I think we should keep using repo.grails.org for now (below the other
> repos, in the repositories block), and await JFrogs ans
We could do that, but I don't think I fully understand the benefit of doing
so.
What are the implications of old artifacts being resolvable?
I guess a fresh start for Grails 7+ artifacts would not hurt given the age
and state of that repository.
Den lör 3 maj 2025 kl 14:47 skrev James Daugherty
:
