On 30/07/11 21:27, Norman Maurer wrote:
Thanks :)
+1
Norman
2011/7/30 Stefano Bagnaraapa...@bago.org:
2011/7/26 Eric Charlese...@apache.org:
Can someone update the sample page. I could do it, but it will be much
faster and safer from mime4j specialists.
On 30/07/11 13:24, Stefano Bagnara wrote:
2011/7/30 Eric Charlese...@apache.org:
On 30/07/11 00:42, Stefano Bagnara wrote:
I guess it's an year or more I don't deploy james websites and I found
I don't know the updated way to do that.
I see the svn folder james/sites/trunk/www is outdated so
Hi,
We need to discuss the way we deploy web sites:
1. Via svn (commit in www project, and update on server).
2. Via svn (commit in www project, and automatically visible via svnpubsub).
3. Via scp (with file permissions issues...)
4. Via mvn site-deploy
I understand there is a consensus for
2011/8/1 Eric Charles e...@apache.org:
Hi,
We need to discuss the way we deploy web sites:
1. Via svn (commit in www project, and update on server).
2. Via svn (commit in www project, and automatically visible via svnpubsub).
3. Via scp (with file permissions issues...)
4. Via mvn
Am 01.08.2011 10:28, schrieb Eric Charles:
o discuss the way we deploy web sites:
1. Via svn (commit in www project, and update on server).
2. Via svn (commit in www project, and automatically visible via
svnpubsub).
3. Via scp (with file permissions issues...)
4. Via mvn site-deploy
I
On Mon, Aug 1, 2011 at 10:18 AM, Norman Maurer nor...@apache.org wrote:
Am 01.08.2011 10:28, schrieb Eric Charles:
o discuss the way we deploy web sites:
1. Via svn (commit in www project, and update on server).
2. Via svn (commit in www project, and automatically visible via
svnpubsub).
2011/8/1 Robert Burrell Donkin robertburrelldon...@gmail.com:
On Mon, Aug 1, 2011 at 10:18 AM, Norman Maurer nor...@apache.org wrote:
Am 01.08.2011 10:28, schrieb Eric Charles:
o discuss the way we deploy web sites:
1. Via svn (commit in www project, and update on server).
2. Via svn
