[
https://jira.codehaus.org/browse/MNG-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321955#comment-321955
]
Jaroslav Tulach commented on MNG-5331:
--------------------------------------
The runtime situation needs different solution. At the end I ended up with the
above mentioned change in pom:
http://source.apidesign.org/hg/bck2brwsr/diff/023cda5b8b0b/rt/launcher/pom.xml
and a reflection hack in runtime:
http://source.apidesign.org/hg/bck2brwsr/diff/023cda5b8b0b/rt/launcher/src/main/java/org/apidesign/bck2brwsr/launcher/WebViewLauncher.java#l1.59
Things seem to work cross-platform on all Oracle JDK's that have JavaFX
included. Btw. I tried to use exec:java, but specifying classpathScope=system
does not include runtime scope and vice-versa. Thus the runtime hack.
> JavaFX should be added to compilation classpath
> -----------------------------------------------
>
> Key: MNG-5331
> URL: https://jira.codehaus.org/browse/MNG-5331
> Project: Maven 2 & 3
> Issue Type: Wish
> Reporter: Konstantin Solomatov
>
> Since JDK 1.7, JavaFX is part of JRE and JDK. However, Maven doesn't include
> them into classpath automatically.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
