[
https://jira.codehaus.org/browse/MNG-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306588#comment-306588
]
Paul Benedict commented on MNG-5331:
------------------------------------
If you have many development and CI machines, I recommend you get a corporate
repository. Tools like Nexus will allow you to publish the JavaFX dependency
one time for everyone. Otherwise, yes, it's the responsibility of each builder
to have the dependency. JavaFX is not unique in this regard. There are many
license-restricted JARs that have this issue (like JavaBeans Activation
Framework); you just need to learn the process for handling these cases.
I hope this link can help ease the pain a bit:
http://java.dzone.com/articles/install-javafx-runtime-local
> JavaFX should be added to compilation classpath
> -----------------------------------------------
>
> Key: MNG-5331
> URL: https://jira.codehaus.org/browse/MNG-5331
> Project: Maven 2 & 3
> Issue Type: Bug
> 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:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
