On 05/07/12 03:31, sebb wrote:
On 6 May 2012 19:45, Robert Burrell Donkin<[email protected]> wrote:
<snip>
Checking generated Maven sites into the CMS (eg [2]) produces lots of commit
messages (eg [3]), and is a little fiddly.
<snip>
I had the same problem with JMeter Javadoc when it was in SVN; I
solved that by post-processing the html files to remove the dates in
the comments.
The same could probably be done in the Maven pom if required.
Cool :-)
I suspect it's possible to wrangle the line ending foo as well
If we're going to switch to the CMS, it will save some effort if we ask
infrastructure to set it up for the new TLP domain.
<snip>
For Maven sites that are generally only updated with each new release,
the fact that Maven sites cannot be built piecemeal is not an issue,
so is it worth the conversion effort?
Rat is sparsely documented, but I had hoped to work on some new,
user-centered content in the CMS and leave the existing stuff for releases.
Unless it is going to change much between releases, it could still be
done by Maven at release time.
+1
However, there might be some restrictions imposed by CMS or Infra as
to which URLs can be used for Maven and non-Maven generated site
files.
Might be an idea to run the plan past infra before doing much work.
+1
We need some form of cohesive top level site for Apache Creadur, hopefully
with some more documentation for users. The consensus seemed to be that
using the CMS fits this well, and allows some products to use Maven and some
to use the CMS for their documentation (by checking the Maven generated
sites into CMS).
For new content, CMS is probably a good choice.
+1
Having tried it for a while, never me nor Stefan are particular keen[1]
about regularly checking in Maven generated sites. I'd be happy just
checking in the Maven generated documentation for each release.
Indeed, Maven-generated sites are best suited for release time docs.
+1
Robert
