Hi Luc,

just take it as a personal experience I want to share: publishing mvn
generated site on ASF svn is not painless, I already experienced it on
Apache Any23 and IMHO using the wagon-svn via maven is a suicide,
because it tries to commit the file one by one :S.

The only more effective "turnaround" I know is the one we use at
Apache Cooon3: checking out locally the site directory, deploying the
mvn site there, then recommitting; in that way, we pay the overhead of
committing the site the first time, but for future deployments the svn
client just sends the deltas. It require a lot of time anyway, just
think about apidocs... :(

That discussion is already open in the Maven dev@ML, hopefully they
will come up with a more effective solution :P

About skin: I am still convinced that adopting fluido-skin would be
better to renew out l'n'f :P

All the best, have a nice day,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/



On Thu, Feb 9, 2012 at 11:38 AM,  <b...@systemoutprintln.de> wrote:
> Hi,
>
> we have a JIRA ticket with a proposal for a new Layout designed by Simo: 
> https://issues.apache.org/jira/browse/COMMONSSITE-65
>
> Regards,
> Benedikt
>
> ----- Original Message -----
> From: luc.maison...@free.fr
> To: dev@commons.apache.org
> Date: 09.02.2012 11:12:30
> Subject: [all] migration to svnpubsub
>
>
>> Hi all,
>>
>> Apache infrastructure policy mandates using svnpubsub to publish project
>> websites by the end of 2012 (see
>> <http://www.apache.org/dev/project-site.html#svnpubsub>).
>>
>> At the same time, a Content Management System has been set up that does
>> abide to this policy (see <http://www.apache.org/dev/cms>).
>>
>> There have been several threads about changing our project site skin
>> recently.
>>
>> Can we pack all this together and make sure we get ready for this change
>> ? Any volunteers ?
>>
>> best regards,
>> Luc
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to