From: Jody G. <jod...@gm...> - 2011-11-20 02:46:59
|
After a bit of exploring I found that the configuration of the javadoc in the modules/pom.xml explicitly set the max memory size. Changing this parameter around a bit still does not allow me to build. I would like to ask that someone on linux (i.e. the same environment as the build box) try compiling the javadocs. I suspect that micheal and myself may be the victim of a mac osx update. Other than that I cannot think of any change that would effect building javadoc that was made to the code base. Second opinion? -- Jody Garnett On Monday, 14 November 2011 at 2:00 AM, Jody Garnett wrote: > The release went fairly smooth; with only one item of note. > > * Unable to produce the javadocs (even with increasing memory). Is there any reason why our javadocs would of require more than twice as much memory as last time? I usually use : > > export MAVEN_OPTS="-Xmx2048m" > > That is no longer sufficient. > > A couple of improvements to the release process: > * build/rename.xml can now update some of the doc references > * updated the release procedure in a few places > > Help needed: > Q: If someone could try a build from source; the extra sanity check would be good. The > Q: Same deal for the tutorials > > We can put the announcement out when the above is ready; release notes are here if you are interested: > - https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10270&version=17864 > > -- Jody Garnett > |