| Excerpt |
|---|
Here you can find information on how to use our useMaven2 based based build environment to work with the Bitmagasin systemstart development on the Bitrepository system. |
The source
Check project out fra https://gforge.statsbiblioteket.dk/svn/bitmagasin. You need to be a registered GForge user to do this.
The building
- Compiling
- Creating distributable
- Releasing
- Handling licensing information
- Testing
- Starting Coordination layer
- Starting clients
The committing
Using the [Atlassian connector|APP:Atlassian connector] and [Atlassian Connector for IntelliJ IDEA|APP:Atlassian Connector for IntelliJ IDEA] will make it much easier to structure your commits according to the following rules:
Commit logical changesets
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.
Commit messages
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.
The details
| Child pages (Children Display) | ||||||||
|---|---|---|---|---|---|---|---|---|
|