There are several open Maven-related issues that seem to have been downgraded. I raised RT-16881 to allow additional comments on these but since this is still pending I am resorting to raising another task instead.

RT-16435 is a simple request to have the JFX DLL's loaded from the classpath instead of from a relative directory. From the response to this and other Maven issues (RT-11182, RT-15732) the official stance seems to be that Maven users will create the tools needed to support JFX2. This is not unreasonable, however in order to build the tools, I believe the DLL's will need to be loaded from the classpath. Maven is just another tool but it is an extremely popular one for business app developers. Hurdles and blocks to Maven tools being built will be hurdles/blocks to JFX uptake in this space.

The change in code should be extremely minor, is there any reason *not* to load the DLLs from the classpath? This would seem like the better way to go anyway - classpath is Java's natural, cross-platform mechanism for loading resources. Using a relative file system path is not a good idea for a lot of reasons.

Cheers,
zonski