Here you can find information on how to use Maven based build environment to start development on the Bitrepository system.
See Common build problems for tips on solving build problems.
- Bitrepository-collection-settings: Contains the Collection settings definitions.
- Bitrepository-message-xml: Contains the Message format definitions.
- Bitrepository-reference: Contains the Reference system code.
- Command-line-client: Containds the code for the Command line client.
- Creating distributable
- Release procedure
- Handling licensing information
- Starting Coordination layer
Before committing your should run the precommit.sh. This will run as automatic QA of the code and attempt to fix trivial problems. See precommit.sh for current functionality.
Commit logical change-sets
When you commit a change to the repository, make sure your change reflects a single purpose: the fixing of a specific bug, the addition of a new feature, or some particular task. Your commit will create a new revision number which can forever be used as a "name" for the change.
All commits should contain a commit message describing the change set. This message must contain the key of the Jira issue related to this commit, this will make all subversion aware applications, able to map issues to change sets.
Adding new files to SVN
If you commit a new file directly to our SVN repository, you must add the SVN property (svn:keywords) for this file to the value: URL Revision Author Date Id
Eclipse will add this automatically for you for all new files if you make sure that auto-props are enabled for subversion. The following modifications to the file $HOME/.subversion/config needs to be made
Add or comment out the line in the [miscellany] section
Add the following to the end of the file: