Author: buildbot
Date: Sun Dec 29 21:22:04 2013
New Revision: 892095
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/contributing.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/contributing.html
==============================================================================
--- websites/production/camel/content/contributing.html (original)
+++ websites/production/camel/content/contributing.html Sun Dec 29 21:22:04 2013
@@ -86,178 +86,40 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><p>There are many ways you can help make
Camel a better piece of software - please dive in and help!</p>
-
-<p>Try surf the documentation - if somethings confusing or not clear, let us
know. Download the code & try it out and see what you think. Browse the
source code. Got an itch to scratch, want to tune some operation or add some
feature?</p>
-
-<p>Want to do some hacking on Camel? Try surfing the our <a shape="rect"
class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue tracker</a> for
open issues or features that need to be implemented, take ownership of an issue
and try fix it.</p>
-
-<p>If you are a new Camel rider and would like to help us, you can also find
some <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12316782";>easy
to resolve issues</a>. Leave a comment on the issue to let us know you are
working on it and add yourself as a watcher to get informed about all
modifications.</p>
-
-<p>If you'd rather a more gentle introduction to working on the Camel project,
how about you try look at the<br clear="none">
-</p><div class="error"><span class="error">Error formatting macro: link:
java.lang.IllegalArgumentException: Link needs a name and a URL as
arguments.</span> </div> and help us get it even more green by supplying more
test cases to get us closer to 100% coverage.
-
- <div class="aui-message problem shadowed information-macro">
+<div class="wiki-content maincontent"><p>There are many ways you can help make
Camel a better piece of software - please dive in and help!</p><p>Try surf the
documentation - if somethings confusing or not clear, let us know. Download the
code & try it out and see what you think. Browse the source code. Got an
itch to scratch, want to tune some operation or add some feature?</p><p>Want to
do some hacking on Camel? Try surfing the our <a shape="rect"
class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue tracker</a> for
open issues or features that need to be implemented, take ownership of an issue
and try fix it.</p><p>If you are a new Camel rider and would like to help us,
you can also find some <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12316782";>easy
to resolve issues</a>. Leave a comment on the issue to let us know you are
working on it and add yourself as a watcher t
o get informed about all modifications.</p><p>If you'd rather a more gentle
introduction to working on the Camel project, how about you try look at
the</p><div class="error"><span class="error">Error formatting macro: link:
java.lang.IllegalArgumentException: Link needs a name and a URL as
arguments.</span> </div><p>and help us get it even more green by supplying more
test cases to get us closer to 100% coverage.</p> <div class="aui-message
problem shadowed information-macro">
<p class="title">Warning</p>
<span class="aui-icon icon-problem">Icon</span>
<div class="message-content">
-
-<p>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. <br
clear="none">
-Until then, please refer to the git usage section on the <a shape="rect"
href="source.html">Source</a> page.</p>
+ <p>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. <br clear="none"> Until then, please refer to the git usage
section on the <a shape="rect" href="source.html">Source</a> page.</p>
</div>
</div>
-
-
-<h2 id="Contributing-Gettingintouch">Getting in touch</h2>
-
-<p>There are various ways of communicating with the Camel community.</p>
-<ul class="alternate"><li>join us on the <a shape="rect"
href="discussion-forums.html">Discussion Forums</a> and take part in any
conversations</li><li>pop by on <a shape="rect" href="irc-room.html">IRC</a>
and say hi</li><li>add some comments to the <a shape="rect"
href="navigation.html">wiki</a></li></ul>
-
-
-<h2 id="Contributing-Improvingthedocumentation">Improving the
documentation</h2>
-
-<p>Documentation is massively important to help users make the most of Apache
Camel and its probably the area that needs the most help!</p>
-
-<p>So if you are interested in helping the documentation effort; whether its
just to fix a page here or there, correct a link or even write a tutorial or
improve what documentation is already there please do dive in and help!</p>
-
-<p>All of the documentation is stored on the wiki. See <a shape="rect"
href="how-does-the-website-work.html">How does the website work</a> or <a
shape="rect" href="how-do-i-edit-the-website.html">How do I edit the
website</a> for more details.</p>
-
-<p>To be able to edit the wiki you need to mail the <a shape="rect"
href="mailing-lists.html">dev list</a> asking for an account (to prevent spam
we only offer access to the wiki by folks sending mail to the mailing list).</p>
-
-<h2 id="Contributing-Ifyoufindabugorproblem">If you find a bug or problem</h2>
-
-<p>Please raise a new issue in our <a shape="rect" class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue tracker</a></p>
-
-
-
-<p>If you can create a JUnit test case then your issue is more likely to be
resolved quicker.<br clear="none">
-e.g. take a look at some of the existing <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/";>unit
tests cases</a></p>
-
-
-
-<p>Then we can add your issue to Subversion and then we'll know when its
really fixed and we can ensure that the problem stays fixed in future
releases.</p>
-
-<h2 id="Contributing-Workingonthecode">Working on the code</h2>
-
-<p>Grab the <a shape="rect" href="source.html">Source</a> and create a project
in your IDE. e.g. if you are using Eclipse the following should do the
trick...</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-svn co https://svn.apache.org/repos/asf/camel/trunk camel
+<h2 id="Contributing-Gettingintouch">Getting in touch</h2><p>There are various
ways of communicating with the Camel community.</p><ul
class="alternate"><li>join us on the <a shape="rect"
href="discussion-forums.html">Discussion Forums</a> and take part in any
conversations</li><li>pop by on <a shape="rect" href="irc-room.html">IRC</a>
and say hi</li><li>add some comments to the <a shape="rect"
href="navigation.html">wiki</a></li></ul><h2
id="Contributing-Improvingthedocumentation">Improving the
documentation</h2><p>Documentation is massively important to help users make
the most of Apache Camel and its probably the area that needs the most
help!</p><p>So if you are interested in helping the documentation effort;
whether its just to fix a page here or there, correct a link or even write a
tutorial or improve what documentation is already there please do dive in and
help!</p><p>All of the documentation is stored on the wiki. See <a shape="rect"
href="how-does-the-website-work.html">Ho
w does the website work</a> or <a shape="rect"
href="how-do-i-edit-the-website.html">How do I edit the website</a> for more
details.</p><p>To be able to edit the wiki you need to mail the <a shape="rect"
href="mailing-lists.html">dev list</a> asking for an account (to prevent spam
we only offer access to the wiki by folks sending mail to the mailing
list).</p><h2 id="Contributing-Ifyoufindabugorproblem">If you find a bug or
problem</h2><p>Please raise a new issue in our <a shape="rect"
class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue
tracker</a></p><p>If you can create a JUnit test case then your issue is more
likely to be resolved quicker.<br clear="none"> e.g. take a look at some of the
existing <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/test/java/";>unit
tests cases</a></p><p>Then we can add your issue to Subversion and then we'll
know when its really fixed and we can ensure that the prob
lem stays fixed in future releases.</p><h2
id="Contributing-Workingonthecode">Working on the code</h2><p>Grab the <a
shape="rect" href="source.html">Source</a> and create a project in your IDE.
e.g. if you are using Eclipse the following should do the trick...</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[git clone
https://git-wip-us.apache.org/repos/asf/camel.git
cd camel
mvn eclipse:eclipse
]]></script>
-</div></div>
-<p>Build the project.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-mvn install
+</div></div><p>Build the project.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[mvn install
]]></script>
-</div></div>
-<p>PS: You might need to build multiple times (if you get a build error)
because sometimes maven fails to download all the files.</p>
-
-<p>Then import the projects into your workspace.</p>
-
-<h2 id="Contributing-Creatingpatches">Creating patches</h2>
-
-<p>We gladly accept patches if you can find ways to improve, tune or fix Camel
in some way.</p>
-
-<p>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 <a shape="rect" class="external-link"
href="http://subclipse.tigris.org/"; rel="nofollow">subclipse</a> plugin.</p>
-
-<p>If you're a command line person try the following to create the patch</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-diff -u Main.java.orig Main.java >> patchfile.txt
+</div></div><p>PS: You might need to build multiple times (if you get a build
error) because sometimes maven fails to download all the files.</p><p>Then
import the projects into your workspace.</p><h2
id="Contributing-Creatingpatches">Creating patches</h2><p>We gladly accept
patches if you can find ways to improve, tune or fix Camel in some
way.</p><p>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 <a shape="rect"
class="external-link" href="http://subclipse.tigris.org/";
rel="nofollow">subclipse</a> plugin.</p><p>If you're a command line person try
the following to create the patch</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[diff -u Main.java.orig Main.java >>
patchfile.txt
]]></script>
-</div></div>
-<p>or</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-svn diff Main.java >> patchfile.txt
+</div></div><p>or</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[svn diff Main.java >> patchfile.txt
]]></script>
-</div></div>
-
-<h2 id="Contributing-Submittingpatches">Submitting patches</h2>
-
-<p>The easiest way to submit a patch is to</p>
-<ul><li><a shape="rect" class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>create a new JIRA
issue</a> (you will need to register),</li><li>attach the patch or tarball as
an attachment</li><li><strong>tick the Patch Attached</strong> button on the
issue</li><li>fire off an email to the <a shape="rect"
href="discussion-forums.html">Discussion Forums</a> linking to the
JIRA</li></ul>
-
-
-<p>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).</p>
-
-<p>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!</p>
-
-<h2 id="Contributing-WorkingwithGit">Working with Git</h2>
-
-<p>While several committer are working with Git, it is not the primary version
control system at Apache Software Foundation. This is because the ASF has to
ensure that each commit into the codebase is correct licensed. With the current
VCS - Subversion - only committers with a signed CLA have write access.</p>
-
-<p>But there are several ways how Git users could improve Camel with their
prefered tool:</p>
-<ul><li>git-svn</li><li>Apache Git Mirror</li><li>Pull request at
Github</li></ul>
-
-
-<p>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 repository.<br
clear="none">
-Depending on the chosen way these steps differ which is short described
here.</p>
-
-<h3 id="Contributing-git-svn">git-svn</h3>
-
-<p>With Git you cannot fork another Git repository - you also could "fork" a
subversion repository.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-git svn clone https://svn.apache.org/repos/asf/camel/trunk
<TargetDirectory>
+</div></div><h2 id="Contributing-Submittingpatches">Submitting
patches</h2><p>The easiest way to submit a patch is to</p><ul><li><a
shape="rect" class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>create a new JIRA
issue</a> (you will need to register),</li><li>attach the patch or tarball as
an attachment</li><li><strong>tick the Patch Attached</strong> button on the
issue</li><li>fire off an email to the <a shape="rect"
href="discussion-forums.html">Discussion Forums</a> linking to the
JIRA</li></ul><p>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).</p><p>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 com
mit 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!</p><h2
id="Contributing-WorkingwithGit">Working with Git</h2><p>While several
committer are working with Git, it is not the primary version control system at
Apache Software Foundation. This is because the ASF has to ensure that each
commit into the codebase is correct licensed. With the current VCS - Subversion
- only committers with a signed CLA have write access.</p><p>But there are
several ways how Git users could improve Camel with their prefered
tool:</p><ul><li>git-svn</li><li>Apache Git Mirror</li><li>Pull request at
Github</li></ul><p>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
repository.<br clear="none"> Depending on the cho
sen way these steps differ which is short described here.</p><h3
id="Contributing-git-svn">git-svn</h3><p>With Git you cannot fork another Git
repository - you also could "fork" a subversion repository.</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[git svn clone
https://svn.apache.org/repos/asf/camel/trunk <TargetDirectory>
]]></script>
-</div></div>
-
-<p>If you have write access to the codebase you could fork from the
https-adress and just "push" your changes back:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-git svn dcommit -m "message"
+</div></div><p>If you have write access to the codebase you could fork from
the https-adress and just "push" your changes back:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[git svn dcommit -m "message"
]]></script>
-</div></div>
-
-<p>Without that privilege you could follow the <a shape="rect"
class="external-link"
href="https://git-wip-us.apache.org/docs/workflow.html";>recommended
workflow</a>: 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.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-git format-patch origin/trunk
+</div></div><p>Without that privilege you could follow the <a shape="rect"
class="external-link"
href="https://git-wip-us.apache.org/docs/workflow.html";>recommended
workflow</a>: 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.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[git format-patch origin/trunk
]]></script>
-</div></div>
-
-<h3 id="Contributing-ApacheGitMirror">Apache Git Mirror</h3>
-
-<p>Forking the Git repo from here is much smoother, because you are forking a
"real" Git repo.</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[
-git fork git://git.apache.org/camel.git <TargetDirectory>
+</div></div><h3 id="Contributing-ApacheGitMirror">Apache Git
Mirror</h3><p>Forking the Git repo from here is much smoother, because you are
forking a "real" Git repo.</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false"
type="syntaxhighlighter"><![CDATA[git fork git://git.apache.org/camel.git
<TargetDirectory>
]]></script>
-</div></div>
-
-<p>Bringing your modifications back to Apache is the <a shape="rect"
class="external-link"
href="https://git-wip-us.apache.org/docs/workflow.html";>same workflow as
described before</a>.</p>
-
-<p>Drawback of this Apache Git repository is that it is a "mirror" with a day
relay. So you are one day behind the community ...</p>
-
-<h3 id="Contributing-PullrequestatGithub">Pull request at Github</h3>
-
-<p>There is also a Git <a shape="rect" class="external-link"
href="https://github.com/apache/camel"; rel="nofollow">repository at Github</a>
which you could fork. Then you 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 to close the pull request because we can't do
that...</p>
-
-<p>Same drawback here - it is one day behind ...</p>
-
-<h3 id="Contributing-Moreresources">More resources</h3>
-
-<p>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:</p>
-<ul><li><a shape="rect" class="external-link"
href="http://wiki.apache.org/general/GitAtApache";>http://wiki.apache.org/general/GitAtApache</a>:
Some basic notes about git@asf</li><li><a shape="rect" class="external-link"
href="http://git.apache.org/";>http://git.apache.org/</a>: List of mgit-mirrors
at ASF</li><li><a shape="rect" class="external-link"
href="https://git-wip-us.apache.org/";>https://git-wip-us.apache.org/</a>: More
Git infos from Apache</li></ul>
-
-
-<h2 id="Contributing-Becomingacommitter">Becoming a committer</h2>
-
-<p>Once you've got involved as above, we may well invite you to be a
committer. See <a shape="rect" href="how-do-i-become-a-committer.html">How do I
become a committer</a> for more details.</p>
-
-<h2 id="Contributing-Usingtheissuetracker">Using the issue tracker</h2>
-
-<p>Before you can raise an issue in the <a shape="rect" class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue tracker</a> you
need to register with it. This is quick & painless.</p>
-
-<p>If you want to have a go at fixing an issue you need to be in the list of
activemq-developers on the issue tracker. To join the group, please mail the
<code>[email protected]</code> mail list with the email address you used to
register with the issue tracker and we'll add you to the group.</p>
-
-<h2 id="Contributing-Becommingacommitter">Becomming a committer</h2>
-
-<p>The first step is contributing to the project; if you want to take that a
step forward and become a fellow committer on the project then see the <a
shape="rect" class="external-link"
href="http://activemq.apache.org/becoming-a-committer.html";>Committer
Guide</a></p></div>
+</div></div><p>Bringing your modifications back to Apache is the <a
shape="rect" class="external-link"
href="https://git-wip-us.apache.org/docs/workflow.html";>same workflow as
described before</a>.</p><p>Drawback of this Apache Git repository is that it
is a "mirror" with a day relay. So you are one day behind the community
...</p><h3 id="Contributing-PullrequestatGithub">Pull request at
Github</h3><p>There is also a Git <a shape="rect" class="external-link"
href="https://github.com/apache/camel"; rel="nofollow">repository at Github</a>
which you could fork. Then you 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 to close the pull request because we can't do
that...</p><p>Same drawback here - it is one day behind ...</p><h3 id="Contri
buting-Moreresources">More resources</h3><p>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:</p><ul><li><a shape="rect"
class="external-link"
href="http://wiki.apache.org/general/GitAtApache";>http://wiki.apache.org/general/GitAtApache</a>:
Some basic notes about git@asf</li><li><a shape="rect" class="external-link"
href="http://git.apache.org/";>http://git.apache.org/</a>: List of mgit-mirrors
at ASF</li><li><a shape="rect" class="external-link"
href="https://git-wip-us.apache.org/";>https://git-wip-us.apache.org/</a>: More
Git infos from Apache</li></ul><h2
id="Contributing-Becomingacommitter">Becoming a committer</h2><p>Once you've
got involved as above, we may well invite you to be a committer. See <a
shape="rect" href="how-do-i-become-a-committer.html">How do I become a
committer</a> for more details.</p><h2
id="Contributing-Usingtheissuetracker">Using the issue tracker<
/h2><p>Before you can raise an issue in the <a shape="rect"
class="external-link"
href="http://issues.apache.org/activemq/browse/CAMEL";>issue tracker</a> you
need to register with it. This is quick & painless.</p><p>If you want to
have a go at fixing an issue you need to be in the list of activemq-developers
on the issue tracker. To join the group, please mail the
<code>[email protected]</code> mail list with the email address you used to
register with the issue tracker and we'll add you to the group.</p><h2
id="Contributing-Becommingacommitter">Becomming a committer</h2><p>The first
step is contributing to the project; if you want to take that a step forward
and become a fellow committer on the project then see the <a shape="rect"
class="external-link"
href="http://activemq.apache.org/becoming-a-committer.html";>Committer
Guide</a></p></div>
</td>
<td valign="top">
<div class="navigation">
