-
Notifications
You must be signed in to change notification settings - Fork 157
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
1.1.x pekko snapshots are no longer including the java 9+ classes #1039
Comments
We need to bisect the commit where this happened |
This is a blocker for 1.1.0, we are published with java 11 , this should not happen. |
Last pekko-cluster-sharding_2.13 snapshot to have JFR classes is 1.1.0-M0+221-959c98db-SNAPSHOT - Jan 9 Missing in next snapshot - 1.1.0-M0+224-ccce5c04-SNAPSHOT (Jan 11) |
nothing obvious but b9d2cc6 was in Jan 9 and that sbt-osgi plugin has been causing us serious grief |
@mdedetrich I reverted b9d2cc6 locally and it fixed the issue with missing JDK9 classes |
Run with java 11 sbt:pekko-stream> show unmanagedSourceDirectories
[info] * C:\Users\hepin\IdeaProjects\incubator-pekko\stream\src\main\scala
[info] * C:\Users\hepin\IdeaProjects\incubator-pekko\stream\src\main\scala-2.13
[info] * C:\Users\hepin\IdeaProjects\incubator-pekko\stream\src\main\scala-2
[info] * C:\Users\hepin\IdeaProjects\incubator-pekko\stream\src\main\java
[info] * C:\Users\hepin\IdeaProjects\incubator-pekko\stream\src\main\scala-2.13+
sbt:pekko-stream> |
Thanks I'll look into it |
So I already know what the likely cause is, its another fallout from sbt/sbt-osgi#64 |
We will need a task to verify the jar contains these Java 9+ classes in the nightly build after packaging. |
So I can indeed confirm that its sbt/sbt-osgi#64, if I print out what the
As you can see the last line is the compiled jdk9 classes which are missing However if we print out the replacement which is
plus
As we can see its missing the JDK 9 classes folder. I will need to do changes in sbt-osgi upstream to fix this |
So I already have a PR ready for sbt-osgi that will allow me to fix this issue, just waiting for sbt/sbt-osgi#118 to get merged. Should be fixed in a couple of days |
after revert the osgi to 0.9.4 and publish local @mdedetrich yes, it's osgi plugin's problem. |
#959 It seems to be caused by this problem. |
@pjfanning Thanks for investigating , this problem is also led to #959. |
I am quite sure that the core problem is what I described at #1039 (comment) which is leading to all of the other described issues. There might be a simple solution for this that doesn't require extending sbt-osgi with additional functionality but I need to first merge + release sbt/sbt-osgi#121 . |
@pjfanning I think this has been solve by #1047 |
My last repeated comment was published in the wrong ISSUE. This comment was published under #1039, that is, we have fixed the compile of the JDK9 class on the package task. You can verify it on latest |
Have a look at the projects/Jdk9.scala file.
The classes that this is supposed to build appear to be no longer built.
Java 1.0.x jars still have the expected classes.
Compare
https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-cluster-sharding_2.13/1.0.2+26-870129ef-SNAPSHOT/
to
https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-cluster-sharding_2.13/1.1.0-M0+283-e597a702-SNAPSHOT/
Have a look for this Java9+ class.
org.apache.pekko.cluster.sharding.internal.jfr.JFRShardingFlightRecorder
Included in the 1.0 jar but not in the 1.1 jar.
This appears to be happening in other jars where we have Jdk9(+) classes.
The text was updated successfully, but these errors were encountered: