Installation into your own Subversion Respository
If you are a Subversion user and you want to experiment a little longer with the z2 -Environment, you will want to commit changes back to the repository so that you can work from different machines and not loose the benefits of a central versioning system.
At this time we recommend an Export from our repository and an import into your repository (the alternative would be a dump, but that would require that you are an SVN administrator).
However, you will need write access to some Subversion repository. Let's say that location has the URL <URL> and is empty.
Please create a folder to work in during the move. It will not be needed anymore when we are done. Open a command line and CD into that folder.
We will assume you are using the command line. The graphical tools will work similarly.
svn export -q http://www.z2-environment.net/svn/z2_base/branches/v2.0/
Provide the user name "z2_base" with password "z2_base" when asked.
When the operation finishes, which may take a little while, you should have a new folder "trunk".
In order to have the runtime know about the new location, we must edit a basic configuration file (otherwise the z2-Environment would not know how to bootstrap):
Open trunk/l0/run/bin/runtime.properties with a text editor (e.g. vi on linux, notepad on Windows).
You will find the following lines:
com.zfabrik.svn.url=http://www.z2-environment.net/svn/z2_base/branches/v2.0 com.zfabrik.svn.user=z2_base com.zfabrik.svn.passwd=z2_base
Change these accordingly. I.e. where it says http://www.z2-environment.net/svn/z2_base replace by <URL> (where <URL> must be replaced by the actual SVN URL that points to the SVN repository location of your choice here and below). Also, replace user name and password with a user and a password that will allow read access to <URL>.
Now import into the other repository by executing:
svn mkdir <URL>/trunk
svn import trunk <URL>/trunk
Done! Now your repository serves the same functionality our repository did. Please make sure to update your core runtime installation, better even: Install it again as in section Installation - it's just a check out after all!
In addition: Do not forget to leave a note from where and at what revision you imported. E.g.
This information will be very valuable when should you decide to upgrade or merge updates.