-
Notifications
You must be signed in to change notification settings - Fork 90
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
Modularization #160
Modularization #160
Conversation
Codecov Report
@@ Coverage Diff @@
## dev-x.2.0 #160 +/- ##
===============================================
+ Coverage 45.48% 45.49% +0.01%
- Complexity 6273 6277 +4
===============================================
Files 372 372
Lines 40140 40137 -3
Branches 6415 6415
===============================================
+ Hits 18257 18262 +5
+ Misses 20711 20707 -4
+ Partials 1172 1168 -4
Continue to review full report at Codecov.
|
Regarding the compatibility questions: Split Packages Internal JDK Types JEP 193: Variable Handles only replaces some of the on-heap use cases Unsafe. In case you're doing anything off-heap, you may need to take a look at the new JEP 370: Foreign-Memory Access API. |
The ProfilerInfoBox is intended to be placed into the ToolBar and provides a quick indication of FX pulse and actual scene frame rates, process and system cpu loads, as well as JDK/JavaFx and (soon) Chart-fx versioning information. N.B. updates are in view of modularising Chart-fx (see also PR #160) Interface to 'com.sun' package interface may become deprecated and/or may cause inconveniences for users that have not yet fully moved to Jigsaw-type modularisation. To be revisited for the 'x.2.y' release.
The ProfilerInfoBox is intended to be placed into the ToolBar and provides a quick indication of FX pulse and actual scene frame rates, process and system cpu loads, as well as JDK/JavaFx and (soon) Chart-fx versioning information. N.B. updates are in view of modularising Chart-fx (see also PR #160) Interface to 'com.sun' package interface may become deprecated and/or may cause inconveniences for users that have not yet fully moved to Jigsaw-type modularisation. To be revisited for the 'x.2.y' release.
d3fd437
to
c241b8a
Compare
We decided to target this for the next major release, so rebased against dev-x.2.0. Also tried to go fully modularized. This removes the need for our custom launcher, but we still need some jvm arguments, mostly due to controlsfx using internal javafx api via reflection. The serialisers also rely on reflection, so there are still some exports missing. On the bright side, we can now start some of our samles without any additional configuration or wrappers. |
3f6440c
to
efef8c6
Compare
Projects missing auto-moudule-name in manifest:
|
0e3f1d7
to
7f8059c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK
* Add auto module name to manifest Adds the `Automatic-Module-Name: <module name>` to the `MANIFEST.MF`which gets packaged into the jar file. The artifactId is used as `<module-name>`. This is a first step towards making chartfx usable for projects using the jigsaw module system as proposed in #156 by @ennerf. * Document steps to be taken to support jigsaw * make module name reverse dns * Remove PerformanceTracker internal api * remove jigsaw todo list
Efforts to make chartfx usable from jigsaw modularized projects as proposed in #156.
Before merging this the following points will have to be addressed:
Jigsaw Compatibility
To make chartfx usable for modularized projects, there are some points which have to be considered according to this blogpost.
So before meging this branch, these issues should probably be adressed.
internal JDK types
Unsafe replacement links to Variable Handles.
unnamed packages
split packages
Are our testcases affecting this? They are in the same package as the implementation but they are not shipped, so it might be ok?
META-INF/services