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.
Twice in recent weeks I have had to patch jellytools sources (as they were referring to some obsolete bundle key in NB main sources rather than the currently used key), and each time I have had to build jellytools manually, running the jar-library target, and copying the built JAR manually into the "builds" dir, in order to get commit validation to pass. Is this really necessary? Can't xtest's build script be made smart enough to use the current jellytools sources, so that we can patch them normally, as is done for other test code?
Well, it was arranged such a way because we didn't want to break tests for accidentally uncompilable jellytools sources. Now, when commit validation uses jellytools we might reconsider this.
For test scripts which imports xtest-qa-functional.xml jellytools jar is built if sources are available. Otherwise it uses jar from jellytools/builds/. /cvs/nbbuild/templates/xtest-qa-functional.xml,v <-- xtest-qa-functional.xml new revision: 1.6; previous revision: 1.5
Needed also changes in jellytools/build.xml: /cvs/jellytools/build.xml,v <-- build.xml new revision: 1.46; previous revision: 1.45