This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 215080 - JavaFX in Swing Project fails during creation with "Project folder already exists and is not empty" error
Summary: JavaFX in Swing Project fails during creation with "Project folder already ex...
Status: RESOLVED DUPLICATE of bug 215088
Alias: None
Product: javafx
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.2
Hardware: PC Linux
: P1 normal (vote)
Assignee: Petr Somol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-02 15:28 UTC by wobster
Modified: 2012-07-03 09:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wobster 2012-07-02 15:28:19 UTC
When I attempt to create a JavaFX in Swing Project and click the "finish" button, the process fails half way through with "Project folder already exists and is not empty" error. When I look at the directory only the nbproject/project.xml artifact was created and everything else is missing.
Comment 1 Stepan Zebra 2012-07-02 18:18:46 UTC
Are you attempting to create the project without a Main class?
Comment 2 wobster 2012-07-03 00:41:53 UTC
Yes. It looks like I was creating a project with "Create Main Class" checkbox unchecked. It works if I check the box.

BTW, why can there only be one run target in a JavaFX project?
Comment 3 Stepan Zebra 2012-07-03 09:51:33 UTC
(In reply to comment #2)
> ...
> 
> BTW, why can there only be one run target in a JavaFX project?

JavaFX projects - including the special JavaFX in Swing type - are designed to follow the JavaFX 2+ deployment scheme:
http://docs.oracle.com/javafx/2/deployment/jfxpub-deployment.htm
You can setup some Run Configurations and switch between them using the config combobox in IDE's toolbar.
If you are referring to the fact that you can't run more than one instance of the same project, that's not currently supported, but it's under development (see issue 212147).

*** This bug has been marked as a duplicate of bug 215088 ***