2013/3/1 Olivier Lamy <ol...@apache.org>:
>> -
>> <commons.scmPubCheckoutDirectory>site-content</commons.scmPubCheckoutDirectory>
>> +
>> <commons.scmPubCheckoutDirectory>${project.build.directory}/site-content</commons.scmPubCheckoutDirectory>
> so if you use mvn clean. You will checkout again the content from svn.
> The goal with using site-content directory is to do only update rather
> than a full checkout even when using clean.
Yes, I know and I thought about that a bit, either solution wasn't
good for me. I don't know how the Commons' release process looks like,
but in the Struts project we always perform release and site deploy
base on clear checkout, which means we must checkout the site anyway.
It would be better to keep site content in a separate folder eg.
../commons-ognl-site-content or in user home folder - I don't what is
better.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
