javafx.base and java.desktop

[Kevin Rushforth]

> Perhaps the module can be declared 'requires static'. 

That was my thinking as well, which is captured in 
https://bugs.openjdk.org/browse/JDK-8240844

Perhaps this is the right time to move this forward?

-- Kevin


On 11/17/2023 4:06 PM, Nir Lisker wrote:
> Hi,
>
> A previous discussion mentioned the removal of AWT dependencies. One 
> of the points that Kevin brought up was
>
>      Refactor Java Beans implementation in javafx.base such that
>     java.desktop is optional
>
>
> John and I looked at this some time ago when we discussed the usage of 
> the javafx base module outside of JavaFX, as its observables/binding 
> capabilities are suitable for non-GUI applications, which currently 
> have to pull in GUI modules as dependencies.
>
> The dependency is used in the property.adapter packages that bridge 
> javafx.base properties with Java Beans. I think that these classes are 
> seldom used.
>
> What could be a way to deal with that dependency? Perhaps the module 
> can be declared 'requires static'. Or extract the adapter packages 
> into a different "interop" module (javafx.javabeans) like javafx.swing?
>
> - Nir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/openjfx-dev/attachments/20231118/66482317/attachment.htm>