cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1018043 - in /websites/production/cxf/content: cache/main.pageCache dosgi-build.html
Date Tue, 12 Sep 2017 10:38:20 GMT
Author: buildbot
Date: Tue Sep 12 10:38:19 2017
New Revision: 1018043

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/dosgi-build.html

Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/dosgi-build.html
==============================================================================
--- websites/production/cxf/content/dosgi-build.html (original)
+++ websites/production/cxf/content/dosgi-build.html Tue Sep 12 10:38:19 2017
@@ -33,7 +33,6 @@
 
 <script src='/resources/highlighter/scripts/shCore.js'></script>
 <script src='/resources/highlighter/scripts/shBrushJava.js'></script>
-<script src='/resources/highlighter/scripts/shBrushBash.js'></script>
 <script>
   SyntaxHighlighter.defaults['toolbar'] = false;
   SyntaxHighlighter.all();
@@ -109,14 +108,12 @@ Apache CXF -- DOSGi Build
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><h2 id="DOSGiBuild-Checkoutsources">Checkout sources</h2><p>Committers
should work directly on the apache git repo and can directly push there.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeHeader panelHeader
pdl" style="border-bottom-width: 1px;"><b>for committers</b></div><div
class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Default" style="font-size:12px;">git
clone https://git-wip-us.apache.org/repos/asf/cxf-dosgi.git</pre>
-</div></div><p>Non committers should clone from our github mirrior as it
makes it easier to provide pull requests</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>for
non committers</b></div><div class="codeContent panelContent pdl">
-<pre class="brush: bash; gutter: false; theme: Default" style="font-size:12px;">git
clone git@github.com:apache/cxf-dosgi.git</pre>
-</div></div><h2 id="DOSGiBuild-FullBuild">Full Build</h2><p>Use
jdk 8 and maven 3</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
-<pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">mvn
clean install
+<div id="ConfluenceContent"><p>The CXF sources are hosted at&#160;<a shape="rect"
class="external-link" href="https://gitbox.apache.org/">Apache gitbox</a>. This includes
a full two way sync with github. As github provides the nicer user interface we now recommend
to directly work on the github cxf repo.</p><h3 id="DOSGiBuild-Webbrowsing">Web
browsing</h3><p><a shape="rect" class="external-link" href="https://github.com/apache/cxf-dosgi"
rel="nofollow">https://github.com/apache/cxf-dosgi</a></p><h3 id="DOSGiBuild-CheckingoutfromGIT">Checking
out from GIT</h3><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">git
clone git@github.com:apache/cxf-dosgi.git</pre>
+</div></div><h3 id="DOSGiBuild-Committing">Committing</h3><p>CXF
committers can directly commit to github after doing the&#160;<a shape="rect" class="external-link"
href="https://gitbox.apache.org/setup/">Apache&#160;gitbox setup</a>. Be aware
that the sync might take half an hour before you are added to the cxf github group.</p><h3
id="DOSGiBuild-FullBuild">Full Build</h3><p>Use jdk 8 and maven 3</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<pre class="brush: bash; gutter: false; theme: Confluence" style="font-size:12px;">mvn
clean install
 </pre>
-</div></div><h2 id="DOSGiBuild-Providingpullrequests">Providing pull requests</h2><p>Make
sure you first open a&#160;JIRA issue with the details of the bug you are fixing or the
requirements you solve when doing an enhancement.</p><p>To create a good pull
request you should:</p><ul><li>fork the CXF-DOSGI github repo</li><li>create
a branch named like the issue id e.g. "DOSGI-100 Improved ..."</li><li>In the
branch ideally have only one commit with a commit message that start with the issue id [DOSGI-100].
This will automatically hook up the PR to the&#160;JIRA issue so we directly see the PR
in&#160;JIRA</li><li>When doing changes in your PR branch you can always squash
commits and do forced push to keep it up to date.&#160;</li></ul><p>Before
pushing make sure you run a full build and it passes. Pull requests with not merge effort
and passing tests have much higher chances to be merged</p><p>&#160;</p></div>
+</div></div><h3 id="DOSGiBuild-Forkingandpullrequests">Forking and pull
requests</h3><p>Make sure you first open a&#160;JIRA issue with the details
of the bug you are fixing or the requirements you solve when doing an enhancement.</p><p>To
create a good pull request you should:</p><ul><li>Fork the CXF-DOSGI github
repo</li><li>create a branch named like the issue id e.g. "DOSGI-100 Improved
..."</li><li>In the branch ideally have only one commit with a commit message
that start with the issue id [DOSGI-100]. This will automatically hook up the PR to the&#160;JIRA
issue so we directly see the PR in&#160;JIRA</li><li>When doing changes in
your PR branch you can always squash commits and do forced push to keep it up to date.&#160;</li></ul><p>Before
pushing make sure you run a full build and it passes. Pull requests with not merge effort
and passing tests have much higher chances to be merged</p><p>See also&#160;<a
shape="rect" href="https://cwiki.apache.org/confluence/pages/viewpage.a
 ction?pageId=69407398">Getting Involved</a></p><p>&#160;</p></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message