Developer Tools Setup and Maintenance¶
_The developer tools covered by this page are collaborative tools like subversion, and trac. Applications for individual work like Eclipse, Firefox, Maven, Cygwin, etc. are covered by DeveloperApplications _
User accounts the collaborative developer tools are managed as regular EDIT accounts which can be created and managed via the EDIT user create form .
- Table of contents
- Developer Tools Setup and Maintenance
The EDIT subversion repository is located at http://dev.e-taxonomy.eu/svn
It is also available through Trac for simple web browsing (but NOT usable for SVN clients!)
You can checkout source code anonymously, but your EDIT login needs to be registered with the system in order to commit. If you feel you need write access, please send a mail to AndreasMueller.
To checkout the cdmlib component for example, type this into your terminal (windows users take a look at tortoise, see link in resources)
% svn co http://dev.e-taxonomy.eu/svn/trunk/cdmlib
The repository contains 3 standard folders: trunk, branches and tags. As the different activities in EDIT share the same repository, all those 3 standard svn folders should have the same substructure on the immediate level below reflecting the component being developed. For example this is the layout of the cdmlib component:
trunk/ cdmlib/ # the active development folder tags/ cdmlib/ # the folder used to store fixed version of the cdmlib, usually releases rel_0.1 rel_0.1b
The trunk/head version for the latest version and active development. Please commit frequently to the trunk, in general at least once per day sounds like a good idea!
Folder containing side branches of the main trunk development line
- When Merging 2 branches, a branch and the trunk or whatever you should always leave a note about the used revision numbers (for the branch(es) and the diff being applied) in the comments of the merging. Otherwise future merging could be problematic!
Folder to store releases or other stable version for referencing.
- Releases should be tagged: release-1.0.0 As a build number for any release it is convenient to use the subversion revision number, as it is unique within the entire repository.
The book ** Version Control with Subversion ** is a very good and complete documentation of subversion available online and for printing.
The project home of subversion can be found at: http://subversion.tigris.org/
Good clients clients include:
Eclipse plugin Subclispe: http://subclipse.tigris.org/
Tortoise for windows: http://tortoisesvn.tigris.org/
Standalone GUI client: http://www.syncrosvnclient.com/
Terminal binaries: http://metissian.com/projects/macosx/subversion/
Advanced subversion configuration:
use the wiki for documenting work in progress and to collaborate.
If you are new to a wiki please start by reading this:
You can mess around and test the wiki formatting on this dedicated page:
Our Trac installation has a wiki RPC interface enabled that allows you to modify wiki pages from within Eclipse. To use this feature please install the following plugin and open the new "Trac" perspective in Eclipse:
see http://www.trac-hacks.org/wiki/EclipseTracPlugin for more
you can copy paste tables from/to excel if you use the following macro in TRAC:
<pre> #!CSV --- your copy-paste data here ---
For example the following text
<pre> #!CSV Name Town Dog Cat Peter London Stevie - Carol Boston - Darren Harald Berlin Friedrich Doris
results in this:
#!CSV Name Town Dog Cat Peter London Stevie - Carol Boston - Darren Harald Berlin Friedrich Doris
See TracNotification for email support.
Tickets & Milestones¶
manage your own work by issuing tickets for tasks to do or use tickets to remember bugs and feature requests for your software development.
In order to assign a ticket to another user, use the account name of that user which is listed at the top of this page
Eclipse Integration w/ Mylyn¶
Mylyn comes with the standard Eclipse Europa edition and allows you to manage your tickets from within Eclipse.