1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
Guidelines for contributing to Hibernate Validator
====
Contributions from the community are essential in keeping Hibernate Validator strong and successful.
This guide focuses on how to contribute back to Hibernate Validator using GitHub pull requests.
If you need help with cloning, compiling or setting the project up in an IDE please refer to
[this page](http://hibernate.org/validator/contribute/).
## Getting Started
If you are just getting started with Git, GitHub and/or contributing to Hibernate Validator there are a
few prerequisite steps:
* Make sure you have a [Hibernate JIRA account](https://hibernate.atlassian.net)
* Make sure you have a [GitHub account](https://github.com/signup/free)
* [Fork](http://help.github.com/fork-a-repo) the Hibernate Validator [repository](https://github.com/hibernate/hibernate-validator).
As discussed in the linked page, this also includes:
* [Setting](https://help.github.com/articles/set-up-git) up your local git install
* Cloning your fork
## Create a test case
If you have opened a JIRA issue but are not comfortable enough to contribute code directly, creating a self
contained test case is a good first step towards contributing.
As part of our efforts to simplify access to new contributors, we provide [test case templates for the Hibernate family
projects](https://github.com/hibernate/hibernate-test-case-templates).
Just fork this repository, build your test case and attach it as an archive to a JIRA issue.
## Create a topic branch
Create a "topic" branch on which you will work. The convention is to name the branch
using the JIRA issue key. If there is not already a JIRA issue covering the work you
want to do, create one. Assuming you will be working from the master branch and working
on the JIRA HV-123 :
git checkout -b HV-123 master
## Code
Code away...
## Formatting rules and style conventions
The Hibernate family projects share the same style conventions. You can download the appropriate configuration
files for your IDE from [the IDE codestyles GitHub repository](https://github.com/hibernate/hibernate-ide-codestyles).
You can very quickly check that you have respected the formatting rules by running Checkstyle:
```shell
mvn checkstyle:check
```
## Commit
* Make commits of logical units.
* Be sure to start the commit messages with the JIRA issue key you are working on. This is how JIRA will pick
up the related commits and display them on the JIRA issue.
* Avoid formatting changes to existing code as much as possible: they make the intent of your patch less clear.
* Make sure you have added the necessary tests for your changes.
* Run _all_ the tests to assure nothing else was accidentally broken:
```shell
mvn verify
```
_Prior to committing, if you want to pull in the latest upstream changes (highly
appreciated by the way), please use rebasing rather than merging (see instructions below). Merging creates
"merge commits" that really muck up the project timeline._
Add the original Hibernate Validator repository as a remote repository called upstream:
```shell
git remote add upstream https://github.com/hibernate/hibernate-validator.git
```
If you want to rebase your branch on top of the master branch, you can use the following git command:
```shell
git pull --rebase upstream master
```
## Submit
* Sign the [Contributor License Agreement](https://cla.jboss.org/) for the Hibernate Validator project.
* Push your changes to a topic branch in your fork of the repository.
* Initiate a [pull request](http://help.github.com/send-pull-requests/).
* Update the JIRA issue, adding a comment including a link to the created pull request.
|
