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.
Product Version: NetBeans IDE Dev (Build 201110040601) Java: 1.7.0; Java HotSpot(TM) 64-Bit Server VM 21.0-b17 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) Parameters set in project properties as unnamed are passed as empty named to deploy script. Are unnamed parameters even allowed in this situation? Shouldn't they be completely filtered out?
Note that this depends on JavaFX issue: http://javafx-jira.kenai.com/browse/RT-17794
Note that this also depends on JavaFX issue: http://javafx-jira.kenai.com/browse/RT-17553
fixed in jetmain http://hg.netbeans.org/jet-main/rev/2cf62323e08f The fix is part of bigger change of jfx-impl.xml build script that enables further improvements and fixes. After this fix the build script behaves conditionally depending on FX SDK version. Unnamed parameters, but also other FX properties are correctly supported from JavaFX 2.0.2 but in FX 2.0 they must not be passed to FX Ant tasks to avoid crash.
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/2cf62323e08f User: Petr Somol <psomol@netbeans.org> Log: FX-version-aware jfx-impl, also fixes #203201 unnamed parameters are passed as named
added correction of a mistake in Ant task setter method name http://hg.netbeans.org/jet-main/rev/1f7121d5f4f8
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/1f7121d5f4f8 User: Petr Somol <psomol@netbeans.org> Log: #203201 follow-up: correct name of argument setter in Ant task
verified in 7.1 FCS