Hi Dan, In order to build offline: It was not enough to merely have the DTD resources on the local machine, as the resources themselves refer to their online URLs.
I had to edit the files to alter all references to local file references. If you diff with the "originals" and my edited ones in trunk/resources you'll see the differences. Hence my response on why I didn't think this was appropriate - and I still don't know how to make the document xml files reference the local copy (no globally vald absolute file path is true on all developers systems? second, settle on "relative to trunk" relative path - requires build from trunk). more below... > Following on from Kevin's work, I've experimented with adding > svn:externals to provide an symlink-sort of effect from > trunk/src/docbkx/dtd-4.5 through to each of the corresponding src/docbkx > directories (eg trunk/src/applib/src/docbkx/dtd-4.5). > > This means two things: > > 1. when you do an svn update, you'll end up pulling down a number of > extra copies of those DTDs. This is normal; don't worry about it. > 2. you should be able to do builds of documentation locally. > > eg > cd applib > mvn site -o > > will build applib docs into applib/target/site/docbkx. > > Let me know if you encounter any problems with this new approach. But first, pull your ethernet cable and disable your WiFi. That'll tell you if it is truly working offline. Regards, Kevin
