yes, and there is nothing in the CMS to detect which source were changed then
which generated content to check-in
we can remove the last published date, that's what is done on pdfbox or tikka.
or accept these commit messages, which aren't really useful, but that's life
Regards,
Hervé
Le mercr
AFAIU, a mvn site build is called on buildbot when changing something.
So as with using cli "last published" is updated for all pages.
2012/3/7 Robert Scholte :
> First I had to find out how to "install" the bookmarklet, but after that
> it's actually quite nice.
> But every change results in a c
First I had to find out how to "install" the bookmarklet, but after that
it's actually quite nice.
But every change results in a commit divided over 4 e-mail messages (ok,
already better than 46).
It updates the "last published" for all pages.
Why not publish only this page? It also shows the
Hello,
http://jira.codehaus.org/browse/MENFORCER-124 suggests a "Rule-scoped
fail property" as feature. My suggestion would be something like this:
- Add an optional qualifier per rule which differentiates between
INFO, WARNING and ERROR (same as the loglevels) and
- Make the rules log with this l
