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.
marina-netbeans-plugin: #42 02-Apr-2009 01:27:52 Product Version = NetBeans IDE 6.5.1 (Build 200903060201) Operating System = Linux version 2.6.20-15-generic running on i386 Java; VM; Vendor = 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05; Sun Microsystems Inc. Steps to reproduce: - Create a JavaFX Script application - Run the application init: deps-jar: ERROR: Unknown profile: desktop /export/home/tester/NetBeansProjects/JavaFXApplication1/nbproject/build-impl.xml:143: exec returned: 255 BUILD FAILED (total time: 0 seconds)
could you attach a verbose log, thanks
Created attachment 79368 [details] Ant verbose log
I cannot verify it as the Hudson is down but my last Linux installation works. Is the installed SDK broken? Please check <nb install dir>/javafx2/javafx-sdk
This exception message comes from javafxpackager and I see no chance to see it as "desktop" is always known profile. Please send me the /lib/shared/toolchain.jar from your installation for analysis. Something similar might only happen with Turkish locales where "mobile".toUpperCase() does not match "MOBILE".
Created attachment 80505 [details] toolchain.jar
The issue is still reproduced. I have attached the toolchain.jar file.
I've decompiled the packager and "desktop" is listed known profile. I have no idea how this may happen unless using some obscure Java version.
JIRA issues: RT-4153 [Linux] Unable to execute JavaFX application: ERROR: Unknown profile: desktop http://javafx-jira.kenai.com/browse/RT-4153 RT-4139 Packager does not properly work after NetBeans installation http://javafx-jira.kenai.com/browse/RT-4139
This bug still happens even in 6.8, 6.9 Beta with Java FX Bundle, 6.9 RC1. It happens on an empty project and on all the samples. My setup is: Red Hat Linux Server 5.5 Desktop Netbeans 6.8, 6.9 RC1, 6.9 Beta, etc.
Verified the same error happens when using Eclipse 3.5 Galileo instead of NetBeans. My OS is Red Hat Linux 5.5 Desktop Server
The workaround should be explicitly setting JAVA_HOME system variable.
(In reply to comment #11) > The workaround should be explicitly setting JAVA_HOME system variable. To what? Java SDK directory? JavaFX SDK directory? I appreciate the responses, but each one means I need to do more Google searches because JAVA_HOME can't be explicitly set in the Netbeans GUI and I don't know how to do it from the command line.
(In reply to comment #12) > (In reply to comment #11) > > The workaround should be explicitly setting JAVA_HOME system variable. > To what? Java SDK directory? JavaFX SDK directory? > I appreciate the responses, but each one means I need to do more Google > searches because JAVA_HOME can't be explicitly set in the Netbeans GUI and I > don't know how to do it from the command line. My JAVA_HOME is currently set to /usr/java/jdk1.6.0.20
According to the comment from the RT-4139 it is the NB issue. http://javafx-jira.kenai.com/browse/RT-4139 JIRA on behalf of Kevin Rushforth wrote: > > This is not a bug in the javafx launchers. As Kumar already commented, the launchers are correctly honoring $JAVA_HOME. This is something that NetBeans itself would need to take care of, or it needs to be documented, possibly in a release note. > > In any case, we are not going to address this in the JavaFX SDK, and certainly not for soma. As such I have lowered the priority to Major and removed the "Fix For" version. > > I would suggest that the next step is to close this JIRA issue as "Will Not Fix" with a link to an appropriate NetBeans bug, once such a bug exists. >
This described case is independent on NetBeans. JavaFX launchers simply do not work when the JAVA_HOME is not correctly set (no matter if launched from NetBeans or command line, no matter if installed together with NetBeans or just a plain JavaFX SDK). I am closing this issue and re-opening http://javafx-jira.kenai.com/browse/RT-4139
If I reproduced the same issue with Eclipse Galileo 3.5, it's still considered a Netbeans issue? (In reply to comment #14) > According to the comment from the RT-4139 it is the NB issue. > http://javafx-jira.kenai.com/browse/RT-4139 > > JIRA on behalf of Kevin Rushforth wrote: > > > > This is not a bug in the javafx launchers. As Kumar already commented, the launchers are correctly honoring $JAVA_HOME. This is something that NetBeans itself would need to take care of, or it needs to be documented, possibly in a release note. > > > > In any case, we are not going to address this in the JavaFX SDK, and certainly not for soma. As such I have lowered the priority to Major and removed the "Fix For" version. > > > > I would suggest that the next step is to close this JIRA issue as "Will Not Fix" with a link to an appropriate NetBeans bug, once such a bug exists. > >
Cleaning bugzilla categories ....