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
Maven site won't be publishable from mvn command line: either you edit it
through the CMS web ui, either directly in classical source svn, but both
edits are then mvn-built by buildbot to staging area, not by the devloper on
his local machine. Of course, everybody can build the site for himself
2012/3/6 Hervé BOUTEMY :
> Le lundi 5 mars 2012 15:26:12 Olivier Lamy a écrit :
>> Hello,
>> Just try it quickly.
> yes, seems to work as expected
>
>> I wonder about calling 'publish site' within a maven plugin.
> I don't understand: with the CMS web ui, you don't have anything on your local
> com
Le lundi 5 mars 2012 15:26:12 Olivier Lamy a écrit :
> Hello,
> Just try it quickly.
yes, seems to work as expected
> I wonder about calling 'publish site' within a maven plugin.
I don't understand: with the CMS web ui, you don't have anything on your local
computer, so I don't see how any local
Hello,
Just try it quickly.
I wonder about calling 'publish site' within a maven plugin.
2012/3/4 Hervé BOUTEMY :
> it would be great if somebody tried some maventest site modification, just to
> check I'm not the only one understanding the CMS :)
> the only limitation is actually that site build
it would be great if somebody tried some maventest site modification, just to
check I'm not the only one understanding the CMS :)
the only limitation is actually that site build by buildbot costs 2 minutes,
and you should not publish before the build is finished
now I thought more on components
as you may have remarked from some "little" commit logs, Joe put a test site
for CMS+svnpubsub of Maven site online [1], with a full CMS integration of
site build using Maven (thank you Joe)
What was done to adapt the site to the CMS integration is quickly documented
in CMS adoption page [2]
