Manual SVN Configuration in Eclipse

• To work with the GSI's SVN repository the first thing you need is a valid Linux account for GSI's ACC cluster. If you do not have an account, please refer to CS-CO-IN, the infrastructure team (ChristophHandel or SteffenSteinmetz)
• To connect to the SVN repository within Eclipse, open Eclipse select the SVN Repository Exploring perspective (Window-->Open Perspective-->Other-->SVN Repository Exploring)
• Select "File-->New-->Repository Location" to define a connection to an existing repository.
• As URL define the following location: https://www-acc.gsi.de/svn/fesa/ or the locations above
• Enter your acc acount login name and password and press finish; if necessary configure Eclipse's secure storage mechanism
• Here you can find a small How-To that tries to cover general SVN handling questions

Internal Information

SVN Usage and Structure

svn:/fesa/framework/[t-b-t]    /fesa-<projects>
svn:/fesa/device/   driver     /[DriverName]/[t-b-t]
                    deploy-unit/[DeployUnitName]/[t-b-t]
                    class      /[ClassName]/[t-b-t]

• [t-b-t] are the ususal subversion folders trunk, branches, tags
• In /fesa/framework you can find all framework elements of the FESA developments @GSI. Read access can be granted on request. Only FESA developers have write permissions.
• In /fesa/device you can find all class, deploy-unit and driver developments. Everybody with a valid GSI ACC account has read and write access.
• Please do not commit generated files, libraries or binaries into the SVN repository. This SVN repository is a source code repository and should not be used for other artifacts.

Background Information on the SVN Layout for FESA3

• FESA is a framework used by multiple GSI departments. For this reason it has its own repository and is not a part of the existing BEL repository.
• In the SVN repository the location of the framework sources and device development sources are separated to avoid irritations of FESA (core) developers.
• Class/driver/deploy-unit are treated as separate artifacts. Each of them can be separately developed and released. So each of them gets its own [t/b/t] structure.
• Deploy-unit source code and associated classes are not directly related.