How to convert a normal java project in intellij into a JavaFx project

One solution is to generate your code using Scene Builder, and then integrate it into your existing IntelliJ project. While it should be possible to import this as a module, you can also simply move the code to where it needs to be (making appropriate corrections to package statements, etc). If you notice that the javafx imports aren't recognized within your project, try this solution:

First ensure that you've set up IntelliJ in general for JavaFX by following the intial steps in this tutorial. Note: Below I mention 1.8, but this should work with 1.7+. I recommend 1.8+.

Second ensure that the existing project settings allow for javaFX use

1. Open Project Structure
2. Click on Project under the project settings pane
3. Ensure that the Project SDK is 1.8+.

Third Ensure that the modules are configured for a JDK supporting JavaFX

1. Open Project Structure
2. Click on Modules under the project settings pane
3. Ensure that the module SDK being used supports javaFX, Again I use JDK 1.8 but it should work with 1.7.

Also, please be aware that if you have a maven project, you may need to put your fxml in a particular location, "/main/resources/". Take a look at this.

That worked for me, and I hope it helps you.

There is nothing to convert.

I don't believe there is any difference in Idea between a "normal" Java project and a JavaFX project.

Sure, in Idea 12.x+ there is a wizard you can use to create a new JavaFX project. But I think that all it does is create a sample hello world application - after initial creation, the way the project works is not any different than any other Java project.

And this is how it should be, JavaFX is just Java. Oracle doesn't differentiate between JavaFX and Java in their distribution, and neither should IDEs in their project types.

I believe, in this case, even if I'm wrong, that I am right enough that it doesn't really matter if I'm wrong.

Update

So I was wrong enough that it matters :-)

Using Idea 13.1.4, if I create a new project using File | New Project | Java, there are the following resource settings (File | Settings | Compiler):

?*.properties;?*.xml;?*.gif;?*.png;?*.jpeg;?*.jpg;?*.html;?*.dtd;?*.tld;?*.ftl

That is, the resources for the project are just set to copy only specific file types. So you could modify it to get the additional file types required in some JavaFX projects by adding resource copying support for fxml and css; i.e, appending ;?*.fxml;?*.css.

The interesting part is that if you create a new project using File | New Project | JavaFX, there are the following resource settings:

!?*.java;!?*.form;!?*.class;!?*.groovy;!?*.scala;!?*.flex;!?*.kt;!?*.clj

Essentially, it's copying everything which not a source file, a kind of file blacklist set rather than a file whitelist set as is used by other project creation templates. Really weird... Anyway, the resource sets are user configurable, so you can modify them as you see fit and once you do so, you shouldn't have any issues (I believe, but I've been wrong before ;-)

Suggestion - Use 3rd party build tools in conjunction with your IDE

You might be better off basing your build off of a 3rd party tool such as Gradle or Maven. Idea works really well with both these external build tools (and others). The advantages of using a 3rd party tool is:

1. Projects with those tools follow a convention where resources are placed in a specific resource folder and everything in that folder is treated as a resource to be packaged in your build output. So there is less confusion there.
2. The resultant projects are more portable and easier to use by other developers who may not be using Idea.
3. The projects can be built easily by continuous integration build systems like Jenkins.
4. Both Gradle and Maven have JavaFX specific plugins which provide additional support for packaging JavaFX applications.

Of course, the disadvantage of using a 3rd party build tool, is the complexity (and many quirks) of learning them as sometimes they can be quite the beast. So I think it's a bit of a tradeoff - small, personal exploratory projects don't need them, larger projects or projects you intend to share with others benefit from using such tools.