I did have some probs with incorrect relative references that I fixed by adding the <url> in the trunk pom and ensuring that it ended with a '/' as a fix for a known bug in the site plugin. This got the breadcrumbs working correctly, for example.
However, I'm not claiming there aren't problems elsewhere, just that I won't have checked everything. Regarding the problems you are having with the docbkx plugin (which is a different plugin to the site plugin), I did try to organise things so that we only needed one copy of the .xsl styles and images, in trunk. But, again, I didn't test this from anywhere other than in trunk, so I could quite imagine it might break if trying to be run at a lower level. There may be better ways to configure some of this stuff, but I'm keen that we try to work *with* maven rather than against it and that we have as little boilerplate as possible in the pom and site files. Everything that's in them currently is there for a reason, if more needs to be added then it should be accompanied by a comment as to why... And that change should be applied consistently across all relevant pom/site files (so we don't get one set of modules working, and another set not) Cheers Dan Sent from my iPhone On 25 Oct 2010, at 17:35, "Kevin Meyer - KMZ" <[email protected]> wrote: > > >> We're not using the maven default skin, it should be out own Isis >> skin (org.apache.isis:classic-skin or something similar) >> >> I wonder if the problem is that you're just building the applib >> module? I must admit I've only ever tried to build the site from >> trunk? Just a thought. >> >> I think that Kevin got the site build running? >> > > I have confirmed that I can only really build documentation from trunk. > > When I tried to build the XML object store (or object store) by itself, I > got errors due to not being able to load html-cust.xsl / cust-fop.xsl > from .../objectstore/src/docbkx/style > > I think there are some config issues affecting builds per module. > > > Also - Dan, anyone? Can you give me pointers to how the relative > directory referencing is managed? All the references work fine from > "near the top", but if you drill down, e.g. into objectstore, then XML, > then certain relative references go to pot. For example, from: > /tmp/m2-sites/isis/alternatives/bytecode/index.html > the relative references to "Maven Report -> Project Information" works, > but "Components -> Application Library" doesn't. > > This happens quite often when you go deeper into some of the links. > > Maybe we are all experiencing symptoms of the same problem - > improper (module relative) path definitions? > > Regards, > Kevin >
