On Fri, 2005-08-05 at 10:49 +0200, Nacho G. Mac Dowell wrote: > Jochen Wiedmann wrote:
<snip> > We'll do it the other way around if it's ok with you. I'll refactor if > it proves to be a pain... > > > I know of no possibility to specify the order. Perhaps the Maven > > mailing list knows? If everything else breaks, use 0api, 1js, 2xs, and > > so on, as subproject names. > > I'll try to investigate the reactor a bit more. it's usually worth mentioning that you're trying to mavenise an apache project when asking on the maven lists <snip> > >> - I like the way the links are currently handled, i.e. not > >> hard-linking them. However, with the xdoc plugin I don't know how to > >> do it. I tried to use i18n: <a key="ext:si".... and, as I expected, > >> it didn't work. Any ideas? Is it the only way through to hard-link > >> them? On february I submitted a patch to allow velocity on > >> user-supplied docs and the project lead seemed quite interested, I am > >> trying again... Another possible approach would be the one I tried: > >> anchors with keys (which makes sense in a i18n world). This would > >> also need a patch though. > > > > > > No idea, sorry. Possibly a > > I am submitting a patch so we can have a hrefkey on anchor tags on the > xdoc plugin. Let's see... is this about the (site) documentation? forrest has a number of features that appeal to jochen (in particular) and make it very suitable for jaxme which i do not think are available through the plain xdoc plugin. i wonder whether there's any way to blend the two in maven. <sigh>shame</sigh> i didn't work this out early (there were lots of forrest folks at the hackathon)... - robert
signature.asc
Description: This is a digitally signed message part
