...
If you'd rather a more gentle introduction to working on the Camel project, how about you try look at the test coverage report and help us get it even more green by supplying more test cases to get us closer to 100% coverage.
Warning |
|
|
| Apache Camel code repository was moved to git, The old svn repo is no longer updated. And this page referring to svn usage must be updated. Until then, please refer to the git usage section on the Source page. |
Getting in touch
There are various ways of communicating with the Camel community.
...
Code Block |
git clone https://git-wip-us.apache.org/repos/asf/camel.git
cd camel
mvn eclipse:eclipse
|
Build the project (without testing).
Code Block |
mvn clean install -Dtest=false
|
PS: You might need to build multiple times (if you get a build error) because sometimes maven fails to download all the files.
...
Most IDEs can create nice patches now very easily. e.g. in Eclipse just right click on a file/directory and select Team -> Create Patch. Then just save the patch as a file and then submit it. (You may have to click on Team -> Share... first to enable the Subversion options). Incidentally if you are an Eclipse user you should install the subclipse plugin.
If you're a command line person try the following to create the patch
...
- create a new JIRA issue (you will need to register),
- attach the patch or tarball as an attachment
- tick the Patch Attached button on the issue
- fire off an email to the Discussion Forums linking to the JIRA
When a ticket is create in JIRA it automatically sends an email to the developer forum but an email always helps alert folks (as lots of emails are generated from every change to every JIRA).
Remember to create and attach the patch in two steps, as JIRA does not support granting ASF license to the patch in the create ticket wizard. So after creating the ticket, then attach the patch and remember to tick off the grant ASF license, otherwise we can not commit the patch. We prefer patches has unit tests as well and that these unit tests have proper assertions as well, so remember to replace your system.out or logging with an assertion instead!
...
- Apache Git Mirror
- Pull request at Github
The minor "problem" is creating the local repository connected to the official repository. Next step is modifying the codebase. The major "problem" then is getting the modifications back to the official ASF Git repository.
Depending on the chosen way these steps differ which is short described here.
Apache Git Mirror
Forking Cloning the Git repo from here is much smoother, because you are forking a "real" Git repoApache git repo.
Code Block |
git forkclone githttps://git-wip-us.apache.org/repos/asf/camel.git <TargetDirectory>
|
Bringing your modifications back to Apache is the same workflow as described before.
Drawback of this Apache Git repository is that it is a "mirror" with a day relay. So you are one day behind the community ...
Pull request at Github
There is also a Git repository at Github which you could fork. Then you submit patches as any other github project - eg work on a new feature branch and send a pull request. For granting the license you also should create a Jira issue with a reference to that pull request. One of the committers then could bring that changesets to the ASF codebase via his/her own local repository. After closing the Jira issue you have needs to accept your pull request to bring the code to the ASF codebase. After the code has been included into the ASF codebase, you need to close the pull request because we can't do that...
Same drawback here - it is one day behind ...
More resources
Git is not a brand new technology and therefore Camel is not the only ASF project thinking about using it. So here are some more resources you mind find useful:
...