I wouldn't use checkstyle, until someone makes a serious effort to
clean up the sources. As soon as someone did, we can very well add the
file later.
I'll leave the checkstyle file but forget about the report for the time
being
Ok, I have a few more questions...
- Do we want a changes.xml for each project? What about contributors?
Should they be on each subproject? I have a mixed feeling here. While I
think that it is a good thing to have them separated it will also be
more painful to mantain. Also, the anouncement plugin expects to have a
changes.xml.
- Does anybody know how to specify the project order on the reactor? It
seems to order them by name...
- In XS SrcContentTest.testSourceFiles expects a system property
"xstc.zip.file", so there is a failure. What is it supposed to be?
- 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.
- The javadoc plugin doesn't generate docs for the tests (at least I
didn't manage directly). This means that (at least in JS) there are
broken links on the docs. Should I use Frederic's suggestion
(maven:addPath ....) for this too?
- What name should I use for the branch, MAVEN?
best regards,
nacho
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
