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 248079 - Maven JavaFX: Corrupt <default config> cannot be edited/deleted
Summary: Maven JavaFX: Corrupt <default config> cannot be edited/deleted
Status: REOPENED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: Dev
Hardware: PC Windows 8.1 x64
: P1 normal with 5 votes (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-21 18:21 UTC by frankv
Modified: 2017-05-25 10:17 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot (108.96 KB, image/png)
2017-03-19 11:21 UTC, tt33jack
Details

Note You need to log in before you can comment on or make changes to this bug.
Description frankv 2014-10-21 18:21:16 UTC
Create a new Maven/JavaFX project, then try to change the project Run settings. All of the settings fields are greyed out, and the warning message "One of Run/Debug/Profile Project actions has been modified and the Run panel cannot be safely edited" is displayed at the bottom of the window.

I'm not sure whether it was something I did, or *how* I managed to corrupt the <default config> Configuration.

It is possible to change the Configuration to "release-profile (Profile)" and then change the other parameters. However, it still won't run... I get the following warnings followed by a bunch of errrors.

Some problems were encountered while building the effective model for frankv:Mapping:jar:1.0-SNAPSHOT
'build.plugins.plugin.version' for org.apache.maven.plugins:maven-source-plugin is missing.
'build.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing.
'build.plugins.plugin.version' for org.apache.maven.plugins:maven-deploy-plugin is missing.

It is highly recommended to fix these problems because they threaten the stability of your build.

For this reason, future Maven versions might no longer support building such malformed projects.


This doesn't apply to a Maven/Java project. It also doesn't apply to a JavaFX/JavaFX Application project.
Comment 1 maxoudela 2015-01-09 09:14:00 UTC
I can confirm that I encounter this bug in Netbeans 8.0.2 and it was impossible to launch the project afterwards...
Comment 2 Tomas Stupka 2015-04-16 15:28:44 UTC
> I'm not sure whether it was something I did, or *how* I managed to corrupt the <default config> Configuration.
just a generic (and in this case misleading) message caused by the fact that the settings "seem" to be changed (even 
though they aren't) as it is not taken in count that the settings UI could be also applied for a javafx app run/debug settings.

looks like, for the same reason as above, changing the settings for a different profile completely messes them up by adding values unrelated to a javafx app
Comment 3 Martin Balin 2016-07-07 08:39:20 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss
Comment 4 McRender 2016-09-16 10:41:45 UTC
I can confirm that I encountered this bug in NetBeans IDE Development Build 201609160002 and it was also impossible for me to launch the project. When I select the project itself and hit run the default JavaFX application gets started. But if I choose an other file with a main() method I always get the following error mesage:  Error: Could not find or load main class
Comment 5 clogs 2016-09-27 10:24:24 UTC
I can confirm that I am unable to add VM parameters to a JavaFX/Maven project in the 'Run' section of the properties. Reopening...
Comment 6 clogs 2016-09-27 10:25:19 UTC
Oh, forgot...this in the RC version of Netbeans 8.2
Comment 7 clogs 2016-09-28 11:23:24 UTC
I am upping the priority to P2. I am unable to debug my JavaFX application from within Netbeans. Does anyone know of a workaround?
Comment 8 tt33jack 2017-03-19 11:21:33 UTC
Created attachment 163884 [details]
Screenshot
Comment 9 chaya 2017-05-25 10:17:52 UTC
got this problem in new project with netbeans 8.2

This solution worked for me:
In Project Properties -> Actions choose configuration with problem.
Then select Run/Debug/Profile project and click "Remove/Reset" button