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.
I created a contrib/sampleapps/htmleditor project and I would like it to work from scratch - e.g. without opening and configuring it in IDE. That is why I modified nbproject/platform.properties to point to $nb_all/nbbuild/netbeans where usually a platform is built using nbplatform.NetBeansFromCVS.harness.dir=../../../nbbuild/netbeans/harness However this does not work - the build script gets confused by usage of relative paths.
I fixed that by http://www.netbeans.org/source/browse/contrib/sampleapps/htmleditor/nbproject/build-impl.xml?r1=1.1&r2=1.2 and now the application can be build from scratch. Shall not similar change be applied to default apisupport templates?
You should not be using a named platform. See harness/README section "USING A RELATIVE PATH FOR THE PLATFORM WITH A MODULE SUITE". Should be analogous for a standalone module, I guess; maybe try netbeans.dest.dir=${basedir}/../../../nbbuild/netbeans harness.dir=${netbeans.dest.dir}/harness Anyway, the proposed patch is not good because the special property task should be setting a property of any kind; if a particular user of that task wants to interpret it as a file location, the calling code can use <property name="..." location="..."/> as usual.