|
[
Permlink
| « Hide
]
Doug Cutting added a comment - 19/Dec/08 05:36 PM
To fix this, I suggest we change build.xml to put generated docs in build/, not docs/. The docs/ directory would be removed.
Attached shell script to be run before patch is applied.
Attach patch to build documentation in build/docs/ rather than docs/. This will not pass Hudson, since it depends on jdiff files that are moved from docs/ to lib/.
Shell the value of the property "build.docs.cn" be "${build.dir}/docs/cn", instead of "${basedir}/docs/cn" ?
Otherwise, patch looks good. I just committed this.
Should we merge this to the 0.19 branch? We will have to adjust release procedures a bit, since the docs for releases will not be in subversion, on the website, they must now, like javadoc, be unpacked from the release rather than retrieved from a subversion tag. Perhaps better to address this now, while it's fresh in our minds, rather than when we get to 0.20? Nigel? This is only committed to trunk, i.e. 0.21, but not yet committed to 0.20.
Doug, let's just commit this to 0.20 (can you merge?). I'll keep track of this issue and do the right things for releases. I'll update HowToRelease wiki when I release 0.20.
> Doug, let's just commit this to 0.20 (can you merge?).
Done. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Closed
Major
do not keep forrest output in subversion
