-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update sbt-osgi to 0.9.6 #31437
Comments
The issue looks easy enough to look into it, but I'm not familiar with the akka build chain. Can you please summarize the steps needed to build the |
I currently tried
But all of them have
Whereas the non-
|
it's in the main akka repo, you can build it with
do you mean perhaps we could simply disable OSGi for that module? |
Thanks, that worked.
No. I was not looking at the correct jar file. I think I located the change in sbt-osgi, which cause your issue. Surprisingly, it was my own PR, haha. As my change fixes another issue, it's rather some incompatibility with protobuf generator setup or my missing deep understanding of sbt. It's this line: sbt/sbt-osgi@bde6dc1#diff-1cb4aa05c813d70c1f075d72300bb104f2d4f5f192264b426e982bd335b693e0R47 I guess I need someone with sbt knowledge to spare me. From fiddling with |
Looks like the change in sbt-osgi causes a race in sbt, which is analyzed here: scala/scala3#11604. Unfortunatelly, this was never reported in sbt-osgi. I guess, a better solution in sbt-osgi is needed then for a proper solution. A workaround could be to override the osgiBundle task to behave as in 0.9.4. |
Closing this as we will instead drop OSGi support. |
Akka currently uses sbt-osgi 0.9.4, which does not seem to work with JDK17 (#31132)
However, when updating to 0.9.6, the
akka-protobuf-v3
artifact does not contain classes anymore, only proto files.The text was updated successfully, but these errors were encountered: