I think it'd be a good idea to incorporate your hack, somehow, so long as it can be done in a way that would work for everyone (eg a file:/// reference, if that works)
Could you pick this up, perhaps, Kevin? Thx Dan Sent from my iPhone On 28 Oct 2010, at 10:31, "Kevin Meyer" <[email protected]> wrote: > >> >> With a -o it zipped along though. Note that an internet connection is >> still required, for the docbkx-maven-plugin to resolve DTDs. > > Yes - I have a problem with this. In my home configuration I've just > spoofed the server in the DTD URL and keep a local copy in my spoofed > server. Couldn't we just use a local (file:// referenced) copy? I mean, > the DTD resources haven't changed in years... > > At the office, which is behind an authentication proxy/firewall, I've > previously edited these resources to be on the local file system. > >> ~~~ > > <snip> > >> >> Second, and perhaps more significantly, my build doesn't try to run >> pdf:pdf. This is right, because for applib there is no pdf.xml file. >> Maybe that's the thing to look into? > > To confirm - mine also runs pdf:pdf (perhaps only sometimes? I must > double check this). > >> >> Anyway, here's my applib output: >> > > I get more warnings (undefined Sinks, etc). > > Could this perhaps be related to the unversioned plugin warnings I > sometimes get? > If we all (Rob, Dan and I) have different versions of some of the plugins, > and no version is explicitly specified, then our respective systems will, > presumably, use whatever version we have installed? > > I seem to remember that you can tell maven to force an error for plugins > that don't have an explicit version. I can't find the reference now, > though. > > >
