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.
If you have specified netbeans.dest.dir using a relative path from suite.dir, rather than using a named platform, it is currently impossible to specify source and Javadoc associations for that platform. It should be made possible somehow - a compatible format extension, plus some support in NbPlatform.java. (In the special case that the platform is in fact ${cvs.netbeans.org}/nbbuild/netbeans, a fully functional source association is automatic; and I think Javadoc association works insofar as you have built Javadoc in place, though that would be unusual.)
I just came across this issue for the first time and would like to say it would be a HUGE help to me as someone developing platform applications.
Perhaps a special pair of property names that could be defined as part of the platform.
Seems to become obsolete after issue #152960, which permits to attach sources and javadoc to clusters using relative path. netbeans.dest.dir should not be set at all in projects using 6.7 harness.
So perhaps FIXED? I don't see a description in EnhancedConfigurationOfNBRCPProjectsImplementation but I haven't checked README yet. According to EnhancedConfigurationOfNBRCPProjectsUISpec there is a GUI to configure it.
It is not in fact fixed, only the situation cannot happen with projects using 6.7 harness, you must either use named platform (with its own way of attaching src & javadoc) or no platform at all, only cluster.path with set of clusters, which can have src & javadoc attached and which use relative paths by default. What was the original use case for not having named platform? Was it to allow RCP developer to checkout sources together with platform from VCS and use them without adding named platform in Platform Manager? If so, I should make this easier using cluster.path, currently you have to add clusters from platform one by one if it isn't a named platform. And README is not updated yet, I'm working on it.
"to allow RCP developer to checkout sources together with platform from VCS and use them without adding named platform in Platform Manager" - exactly. "currently you have to add clusters from platform one by one if it isn't a named platform" - probably not an issue; most RCP devs are going to be using 1-3 clusters only, and if the setup is kept in VCS then this needs to be done only once anyway.