Jochen Wiedmann wrote:
Choose the approach, which is more simple. If we want, we can change
later.
I've already taken the more complicated approach :-[
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.
The property is used by the test case "TestSrcContent". Note, that the
Ant script invokes only test cases with the suffix "Test". In other
words, that test is intentionally not invoked by the test suite.
Doh!
- 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...
nacho
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
