> 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
