davisusanibar commented on PR #13072: URL: https://github.com/apache/arrow/pull/13072#issuecomment-1731904205
> @danepitkin: In case it's applicable here, I recently noticed RoaringBitmap upgraded to JPMS w/o needing to drop support for Java 8, see [RoaringBitmap/RoaringBitmap#657](https://github.com/RoaringBitmap/RoaringBitmap/pull/657). It looks like it requires dropping support for _building_ with Java 8 (must be built with Java 11+) but the result can still be run under Java 8. I'm not familiar with a lot of the details so I can't say if this same approach would help here but I thought I'd share. Hi Team, yes, there are some solutions available for implementing JPMS ad target/release to JDK8, the main problem is that these solutions will fail if a project has Unsafe dependencies. Consider: https://github.com/apache/arrow/pull/13072#:~:text=Implement%20cross%2Dcompilation,jeps/247 and [JEP-247](https://openjdk.org/jeps/247#:~:text=For%20N%20%3E%3D%209%2C%20the,image%20is%20not%20allowed.). The PR was moved around to include module-info.java files **to validate only JPMS requirements** and ensure that we are prepared to implement them after JDK8 deprecation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
