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 visitor how old the
information on that page is.
I'm pretty sure there are pages which suggest to be up to date but are in
fact outdated or even wrong nowadays.
-Robert
Op Wed, 07 Mar 2012 05:10:14 +0100 schreef Hervé BOUTEMY
<[email protected]>:
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
on his
local machine, but not for publication: for the moment, we let the CMS
do the
publication of his own builds.
This is different from components, where the CMS won't be used neither
to edit
nor build+publish: here, the developer will build the component site on
his
local machine then commit the locally-staged site to svn (with
asf-svnpubsub-
plugin if we try to keep a consistent history, or something even more
simple/brutal if we don't). And since the svn we talk about here is
diretly
the production site svn, the modifications will be directly available to
the
public site
Regards,
Hervé
Le mardi 6 mars 2012 00:27:02 Olivier Lamy a écrit :
2012/3/6 Hervé BOUTEMY <[email protected]>:
> 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 Maven invocation could
> help
I mean when deploying tru cli using the classic mvn site (which will
commit to svn). We will need it for sub projects etc..
So after commit we will need to publish the site tru cms (or maybe I
miss something :-) )
> Regards,
>
> Hervé
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
