In the meantime, I found an elegant workaround: My project is still a native JavaFX project, but I changed the build.xml according to this instructions: http://wiki.netbeans.org/FaqMavenAntTasks. Whenever I´m doing a build, now, the pom.xml is checked for updates and all dependencies are added to the classpath in project.properties.
On Apr 17, 1:37 am, Steven Herod <steven.he...@gmail.com> wrote: > For me, 'right click, fix imports' x2 is now muscle memory :o) > > I'd be interested in how the mavenized JavaFX build works. I'm > building and running from inside Netbeans only. > > On Apr 16, 12:52 am, Ryan Waterer <aguitadel...@gmail.com> wrote: > > > I've been working with Netbeans and JavaFX recently. It's still very > > early, so I wouldn't be surprised > > if the two don't play very nice together. To give you an example of how > > early -- > > code completion and code formatting barely work, and only if you're lucky. > > > On Wed, Apr 15, 2009 at 7:00 AM, Lars Bollen <larsbol...@gmail.com> wrote: > > > > Hi all, > > > > does anybody have experience with using NetBeans to work on a > > > mavenized JavaFX project? It seems to me that I can have either a > > > Maven project or a JavaFX project, but not both at a time. > > > > For once, I would be glad if someone would prove me wrong. :-) > > > > Regards, > > > Lars --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
