i have newly configured jboss 7 web profile for a potential migration we will do from jboss 4. i was asked to commit my entire jboss 7 to subversion so another developer could look at it. here's how i did it, the errors i got during the process and how i overcame them.
on my local machine (where i have the jboss source), log into the remote svn server:
ssh mySshUser@myRemoteSvnServer
(i'm now) on
myRemoteSvnServer (ip address:
192.168.1.254), create the new svn repo:
sudo svnadmin create /srv/svn/repos/jboss-as-web-7.0.2.Final
now copy the password file from another svn project (the same people will be allowed to access this jboss project):
sudo cp -f /srv/svn/repos/anotherSvnProject/conf/passwd /srv/svn/repos/jboss-as-web-7.0.2.Final/conf/
otherwise just edit the new repo password file, defining who has access to it, etc.
now make sure the ownership of the new repo is correct:
sudo chown -R www-data:www-data /srv/svn/repos/jboss-as-web-7.0.2.Final
on my local machine, import the jboss source to the new, remote repo you just created:
svn import /path/to/jboss/source/jboss-as-web-7.0.2.Final https://192.168.1.254/svn/jboss-as-web-7.0.2.Final
on
myRemoteSvnServer, just to be sure, make sure ownership is correct again:
sudo chown -R www-data:www-data /srv/svn/repos/jboss-as-web-7.0.2.Final
---
along the way i got various errors:
svn: OPTIONS of 'http://192.168.1.254/svn/jboss-as-web-7.0.2.Final': could not connect to server (http://192.168.1.254)
svn: Your commit message was left in a temporary file:
svn: 'svn-commit.tmp'
this was most likely due to the fact that the remote svn server actually runs on https, not http.
svn: Can't open file '/srv/svn/repos/jboss-as-web-7.0.2.Final/db/txn-current-lock': Permission denied
svn: Your commit message was left in a temporary file:
svn: 'svn-commit.2.tmp'
this was most likely due to a permissions/ownership issue, so i ran this on the remote svn server:
sudo chown -R www-data:www-data /srv/svn/repos/jboss-as-web-7.0.2.Final
