JavaFX On IOS Using RoboVM And Maven
zonski at gmail.com
Fri Aug 2 02:31:08 PDT 2013
What third party libs are you using?
Basically you should use the standard maven way of including dependencies which means adding a dependency entry to your pom.xml.
So if you want MigLayout for example you would add:
This will download the jar and add it to your classpath. The robovm plugin will then include this in the robovm build.
See this for more details: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
A lot of libraries most people use are in maven central: http://search.maven.org/
But if it's something not in central you can add it to your own system manually:
Let me know if you need more info.
On 02/08/2013, at 5:28 PM, Tobias Bley <tobi at ultramixer.com> wrote:
> Hi Daniel,
> thanks for your great work!
> One question: How can I use third party jar libraries? When I execute the „compile“ maven task, my third party libs are not found…
> Am 01.08.2013 um 05:34 schrieb Daniel Zwolenski <zonski at gmail.com>:
>> The RoboVM Maven plugin is now released with JFX support using Danno's
>> backport, which is all in Maven Central.
>> I talk about it in detail here:
>> I'd greatly appreciate people here trying it out and letting me know fairly
>> quickly if there are any steps I left out or if anything is not working (in
>> terms of the hello world, not bigger issues at this stage).
>> Every time I release or publish something I get a lot of "I don't know how
>> to code and couldn't get past step 2" type requests. These can be very time
>> consuming to work through, since some are real and some are just
>> stupid-user-exceptions. Anything I can head off at the pass is a boon.
>> As per the post, yes, it's slow, yes, it's buggy, yes, it all looks pretty
>> crap at the moment - but it's suppose to. The JFX code has barely been run
>> by the people who wrote it and the RoboVM code is being developed by one
>> guy part time and has not been optimised at all. The fact that it works at
>> all is down right amazing.
>> The point of releasing this code is so the above issues can start being
>> addressed, it's not meant to be perfect. If you want it better, I'm sure
>> Niklas, Danno and Richard are only too happy for you to help out in each of
>> the respective areas where there are known issues.
>> No one ever wants to help out with the build tools, that's a crap job that
>> no sane person would do in their spare time :)
More information about the openjfx-dev