SubversionServer

From NeXus
Jump to: navigation, search

NeXus definitions (both base classes and instruments) and the NeXus library source code are held in a subversion repository. The repository is world readable and though you can browse the NeXus library and applications or NeXus definitions repositories directly, but a better looking interface is provided by the ViewVC or TRAC browsers.

The repository can alse be interrogated for recent updates via a query form e.g show me all Library or Definition changes in the last month.

If you wish to receive an email when a change is made to the repository you should join the appropriate Mailing Lists. Alternatively, you can use an RSS feed to keep an eye on changes - TRAC supports this on pages with an orange "XML RSS Feed" icon at their foot such as:

Anonymous Read-only subversion access

Read only access to the subversion repository is via a "http" link. The URL of the subversion repository: http://svn.nexusformat.org/code/trunk (for library/applications) or http://svn.nexusformat.org/definitions/trunk (for definitions)

svn co http://svn.nexusformat.org/code/trunk nexus_code

Login for Write access

Read/Write access to the subversion repository must be via an "https" rather than "http" link. To update files in these repositories you will need to use a program such as TortoiseSVN and also provide your NeXus Wiki username and password. Note that for subversion write access:

Other information you will need to give to access are:

svn co --username "My WIKI Username" https://svn.nexusformat.org/code/trunk nexus_code

Please report any problems via out the IssueReporting system

Committing Changes

As well as needing a valid account, you will not be able to check-in changes unless you indicate (in the log message attached to the commit) which current issues on the IssueReporting system the changes either fix or refer to. This is done by enclosing special phrases in the commit message of the form:

command #1
command #1, #2
command #1 & #2 
command #1 and #2

where command is one of the commands detailed below and #1 means "issue number 1" on the system etc. You can have more then one command in a message. The following commands are supported and there is more then one spelling for each command (to make this as user-friendly as possible)

For example the commit message

    Changed blah and foo to do this or that. Fixes #10 and #12, and refs #12.

This will close issues #10 and #12, and add a note to #12 on the IssueReporting system. For a list of current issues see:

Personal tools
Namespaces
Variants
Actions
Navigation
Documentation
Print/export
Toolbox