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
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 wrote:
> I've been working with Netbeans and JavaFX recently. It's still very
> ear
On Apr 15, 3:00 pm, Lars Bollen 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.
You're right. Here's what Petr Hejl, the maintainer
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,
