Page History

...

If you'd rather a more gentle introduction to working on the Camel project, how about you try look at the

{link:test coverage report|http://nemo.sonarsource.org/dashboard/index/org.apache.camel:camel}{link}

and help us get it even more green by supplying more test cases to get us closer to 100% coverage.

...

Grab the Source and create a project in your IDE. e.g. if you are using Eclipse the following should do the trick...

svngit coclone https://svngit-wip-us.apache.org/repos/asf/camel/trunk camel.git
cd camel
mvn eclipse:eclipse

Build the project.

mvn install

PS: You might need to build multiple times (if you get a build error) because sometimes maven fails to download all the files.

...

If you're a command line person try the following to create the patch

diff -u Main.java.orig Main.java >> patchfile.txt

or

svn diff Main.java >> patchfile.txt

...

With Git you cannot fork another Git repository - you also could "fork" a subversion repository.

git svn clone https://svn.apache.org/repos/asf/camel/trunk <TargetDirectory>

If you have write access to the codebase you could fork from the https-adress and just "push" your changes back:

git svn dcommit -m "message"

Without that privilege you could follow the recommended workflow: working on a feature branch, create a patch and attach it to Jira. Attaching to Jira has the benefit for the community that you are enforced to grant explicitly the license to the ASF.

git format-patch origin/trunk

...

Forking the Git repo from here is much smoother, because you are forking a "real" Git repo.

git fork git://git.apache.org/camel.git <TargetDirectory>

...