Community
Participate
Working Groups
2. Project properties / Javadoc Location Couple of issues with this setting. I am unable to set this to: ${project_loc}/local/javadoc/API_provisioning/ because the properties setting requires the directory to be present and contain the files package-list and index.html. The directory and files are not present because our Javadoc is a part of the build and is therefore under our output directory tree "local". This property needs to have an "Allow output folders for Javadoc location" option.
Move to JDT/UI
Martin, can you please comment.
So far Javadoc location does not support any variables.
If Javadoc location does not support variables as you say, then the Javadoc facilities of Eclipse are useless to my large team (projects are checked out to various folders, etc.)
Changing title to "Javadoc location should support variables". An alternative is to use Ant to build the Javadoc. Ant does support variables which can be bound to predefined Eclipse variables. See the "environment tab" of the run configuration for ant files. Supporting variable in Javadoc export wizard is time permitted.
Thank you for the suggestion, but we already have an ANT target to build the JavaDoc. The point is that we are encouraging developers to operate within Eclipse, thus the need to support variables in the Javadoc location (which is fully supported in the launchers, external tools, etc...Javadoc gen is now inconsistent and effectively unusable for team development). Cheers,
Reopen to close as dup of bug 67020.
*** This bug has been marked as a duplicate of 67020 ***