grons for Pekko (open source akka)

[normana400]

now that the Pekko (aka open source) fork of akka is live (latest version is currently 1.0.1), is there a planned implementation of support for pekko.
essentially it should work like the metrics4 akka lib (but with different artifacts / package names)

https://pekko.apache.org/docs/pekko/current/project/migration-guides.html

[erikvanoosten]

Hi @normana400 . If there is interest, a Pekko version can be created for sure!

I have not used metrics-scala in any project for over 5 years, so it is not high on my priority list. I would definitely support a pull request though.

[normana400]

#483

[erikvanoosten]

Looks good! I'll take a more thorough look tomorrow.

[erikvanoosten]

This is included in version 4.3.0 that was just released. 🥳

We need to figure out the compatibility rules of Pekko to update some names. But this is not urgent.

[normana400]

class names are the same.
every package name starting with "com.typesafe.akka..." or "akka" now is "org.apache.pekko..."
that idea also pertains to artifact names except for kafka streams / alpakka which is named: "pekko-connectors-kafka"

typesafe configs that were akka{} are now pekko{}

I think that is the gist of the dfferences in naming

[erikvanoosten]

I meant compatibility rules between different pekko versions 😄

[erikvanoosten]

... as those determine the versioning scheme for metrics-pekko.

[sylvoutt]

sorry for my answer, i need your version with pekko but you didn't publish it on maven like the other. It's a choice ?

[erikvanoosten]

Ehh, ☺️
It seems you are correct! I'll take a look when I am back from my holidays.

[erikvanoosten]

I am back from my holiday. I did some research but I do not understand what went wrong at all.

Unfortunately, my sonatype account got disabled. As soon as that is fixed I will do a new release, this time hopefully including the pekko module. Meanwhile, I will create a new issue.

[erikvanoosten]

Now that the situation is resolved I can write a bit more. My Sonatype account got disabled because of MavenGate. It is not clear why nl.grons came on the 'vulnerability' list though. My current assumption is that it was a mistake. I wrote a bit about the situation on https://day-to-day-stuff.blogspot.com/2024/08/mavengate-gets-it-all-wrong-and-hurts.html

This does not explain why the previous artifacts are missing in maven central. Unfortunately, I do not know of a way to investigate this further so I am leaving it at that.

cc: @sylvoutt

[sylvoutt]

@erikvanoosten Thanks a lot