Thanks for the update James and awesome ;)
It was the only part that I planned to verify ;)
The other things is the way that we publish the documentation on the
website (the location on people.apache.org especially).
Thanks again,
Regards
JB
On 03/09/2012 09:03 AM, James Strachan wrote:
FWIW scalate:deploy is using pretty much identical code under the
covers- reusing the same mvn wagon stuff to do the upload; so I'd have
thought it'd just work.
On 9 March 2012 07:45, Jean-Baptiste Onofré<[email protected]> wrote:
Hi all,
as you probably know, the Apache Infrastructure team has mandated that all
projects move to the new svnpubsub process for publishing their website by
the end of the year.
The purpose is to reduce the sync time and the I/O required to the sync.
The Infra worked with the Maven team, and a simple mvn site:deploy works
fine.
However, as our website use scalate, we do:
mvn install
mvn scalate:deploy
So it's not a pure mvn site:deploy.
I'm going to discuss with Joe (from the Infra) to see if it could work "out
of the box" using scalate:deploy or if we need to perform some update on
scalate to use something similar to site:deploy.
A possible workaround is to use:
mvn scalate:sitegen
mvn site:deploy
I think it should work.
I will keep you posted about that.
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
