Hello Steve,
> >Well, basically I cannot build "dist" for meta and lifecycle > because of missing test targets. "dist" for assembly fails > because of missing file "KEYS". I build "javadocs" for these > targets now. > > > > This is well into an untested area. > Thanks for for taking the time on this! Thought so. > >I do not know wether "dist" would normally copy the > generated docs, but I had to adjust for the "javadoc" target > any of the references. > > > > With the recent reshuffling I'm experiencing problems getting > document > generation working properly. Internally I using an xdoc build and > figure that I can revert back to classic avalon doc > generation once the > wrinkles are worked out. Aside from that I'm not keen on > putting much > time into fixing the doc gen side prior to resolving the > question of a > project management infrastructure (maven/centerpede etc.). Perfectly clear. Writing code is much more fun :) > Anyway - the > above changes ensure the the API are built correctly - and that's the > immediate priority. There is one drawback now. These local links allow to build the javadocs, but if you create a dirstibution that is internally shared among a team of developers, this won't work either. Looking at javdoc I found a solution for this: ============= snip ========== -linkoffline extdocURL packagelistLoc This option is a variation of -link and accomplishes the same external referencing. The differences here is that you specify a package-list location that is on your local machine. This allows you to overcome the constraint of your Javadoc having web access to the external URL at the time you generate the documentation. This is extremely useful if you are generating your Javadoc documentation from inside a firewall or proxy for instance. ============= snap ========== I think I will give it a try and send a patch, if I come up with something useful (so you can concentrale on something more valuable <g>). BTW: The essential J2SE and J2EE linkks could be defined in a default.properties at the sandbox home - is it OK to create this one? Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
