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.
From issue #54161: "a complete description of the new format should be included in apisupport/harness/release/README"
/cvs/apisupport/harness/release/README,v <-- README new revision: 1.46; previous revision: 1.45
fixed
Documentation seems inadequate. To be answered: - whether all test roots need to be listed even if defaults would suffice for some - whether the tested module itself has to be explicitly listed as a dep if <test-dependencies> is specified - how exactly <recursive/> and <compile-dependency/> interact: addition to run CP same as addition to compile CP, or potentially different? - whether <test/> implies non-<test/> dep also http://apisupport.netbeans.org/TestDistAndDep.html does not seem precise enough. E.g. "The recursive property is used only for module dependency. It adds on classpath all modules which needs the module defined code-name-base to be enable in running IDE." implies that it will automatically add provide-require dependencies too, which I guess it does not.
thanks for comments, I will attach new version of README, can you look at it if something is missing?
Created attachment 33131 [details] README.diff
"below" is č. "pod". "bellow" is č. "křičet" or similar. So s/bellow/below/g. - <!-- Always available when running, but to include at compile time also: --> + <!-- Always available when running, but to include at compile time also. --> - <!-- To request the tests of that module, rather than the module itself: --> + <!-- To request the tests of that module, rather than the module itself. --> unnecessary. "unittests" -> "unit tests" "Runtime module dependencies are added on compile and runtime classpath of tests" is pretty vague and would be better rewritten or just omitted. The examples would better say that you are adding test deps from a fourth module, D, and explain Use #1: compile=D, run=A+D #2: compile=D, run=A+B+C+D #3: compile=A+B+C+D, run=A+B+C+D #4: compile=A+B+C+D+A/unit, run=A+B+C+D+A/unit Still need to mention that for test roots which are not explicitly listed, behavior is equivalent to <test-type> <name>whatever</name> </test-type> i.e. just this module's JAR is included in compile and run classpaths.
Jesse, thanks a lot for you comment. Checking in README; /cvs/apisupport/harness/release/README,v <-- README new revision: 1.48; previous revision: 1.47 done