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.
When integrating the NetBeans harness into existing build system of one NetBeans Platform customer, we find out that the default build directories (e.g. suite/build and suite/module/build) are polluting the system state. The official policy is to put things under some separate directory like $VEDMA/target. Can the harness scripts be modified to provide a single to use property that we can just point to such directory? ant -Dbuild.suite.dir=$VEDMA/target/nb-app/ and all the temporary files would be created under this directory?
Working on it. Not easy; there are a lot of subtle dependencies on the order in which various properties are initialized which cannot be easily predicted.
core-main #ecaedb980370
Integrated into 'main-golden', will be available in build *201007030001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/9a2794a426fb User: Jesse Glick <jglick@netbeans.org> Log: Testing at least the harness portion of #188210.
Integrated into 'main-golden', will be available in build *201106031000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/cdd02e65d2a6 User: Jesse Glick <jglick@netbeans.org> Log: Ability to put most nb.org build products in a separate location (nb.build.dir). Similar to #188210 but for the nb.org source tree, rather than an external suite. Tested on a clean source tree with nbbuild/user.build.properties containing: cluster.config=minimal nb.build.dir=<SOMEROOT>/nbide netbeans.dest.dir=${nb.build.dir}/netbeans netbeans.build.dir=${nb.build.dir}/build test.dist.dir=${nb.build.dir}/testdist public.package.jar.dir=${nb.build.dir}/public-package-jars using: mkdir -p <SOMEROOT>/nbide/netbeans && ant Do not expect apisupport.project's evaluator to understand the nonstandard path locations, i.e. this mode may be used to perform batch builds but is not suitable for interactive development. To check for unwanted build products in this cluster config besides currently known violations: hg st -i -X nbbuild/user.build.properties -X '*/external/*' -X 'nbbuild/build/antclasses/**' -X nbbuild/nbantext.jar -X 'nbbuild/nbproject/private/scan-cache-*.ser' -X 'nbi/infra/lib/**' -X 'nbi/infra/build/**' -X nbi/engine/dist/nbi-engine.jar -X 'nbi/engine/build/**' -X nbbuild/build/createlicensesummary.xml -X 'db.sql.visualeditor/src/org/netbeans/modules/db/sql/visualeditor/parser/*' -X 'applemenu/eawtstub/build/classes/**' -X applemenu/eawtstub/dist/eawtstub.jar -X 'csl.api/anttask/build/classes/**' -X csl.api/anttask/build/cslanttask.jar -X db.sql.visualeditor/build/javacc.jar
*** Bug 219721 has been marked as a duplicate of this bug. ***