You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2014/09/23 16:00:12 UTC
svn commit: r923251 - in /websites/staging/jena/trunk/content: ./
documentation/query/ documentation/sdb/ documentation/serving_data/
download/ getting_involved/ help_and_support/
Author: buildbot
Date: Tue Sep 23 14:00:12 2014
New Revision: 923251
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/query/download.html
websites/staging/jena/trunk/content/documentation/sdb/index.html
websites/staging/jena/trunk/content/documentation/serving_data/index.html
websites/staging/jena/trunk/content/download/maven.html
websites/staging/jena/trunk/content/getting_involved/index.html
websites/staging/jena/trunk/content/help_and_support/bugs_and_suggestions.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 23 14:00:12 2014
@@ -1 +1 @@
-1625614
+1627032
Modified: websites/staging/jena/trunk/content/documentation/query/download.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/download.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/download.html Tue Sep 23 14:00:12 2014
@@ -146,9 +146,6 @@
<div id="breadcrumbs"></div>
<h1 class="title">ARQ Downloads</h1>
<p>For details on downloading ARQ, please see the Jena <a href="/download/index.cgi">downloads page</a>.</p>
-<h2 id="subversion">Subversion</h2>
-<p>Access to the live development version, including a complete
-Eclipse project, is available <a href="https://svn.apache.org/repos/asf/jena/trunk/jena-arq/">via SVN</a></p>
<p><a href="index.html">ARQ documentation index</a></p>
</div>
</div>
Modified: websites/staging/jena/trunk/content/documentation/sdb/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/sdb/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/sdb/index.html Tue Sep 23 14:00:12 2014
@@ -186,9 +186,6 @@ TDBs substantially better performance an
<h2 id="downloads">Downloads</h2>
<p>SDB is distributed from the Apache Jena project. See the
<a href="/download/index.cgi">downloads page</a> for details.</p>
-<h2 id="subversion">Subversion</h2>
-<p><a href="https://svn.apache.org/repos/asf/jena/trunk/jena-sdb">SDB subversion repository</a>
-at Apache.</p>
<h2 id="support">Support</h2>
<p><a href="/help_and_support">Support and questions</a></p>
<h2 id="details">Details</h2>
Modified: websites/staging/jena/trunk/content/documentation/serving_data/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/serving_data/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/serving_data/index.html Tue Sep 23 14:00:12 2014
@@ -601,24 +601,6 @@ with any compliant SPARQL 1.1 system off
<p>See <code>UpdateExecutionFactory.createRemote</code></p>
<h3 id="sparql-http">SPARQL HTTP</h3>
<p>See <code>DatasetAccessor</code></p>
-<h2 id="development-system">Development System</h2>
-<p>If you wish to pick the development codebase, check out the
-codebase from Apache:</p>
-<div class="codehilite"><pre> <span class="n">svn</span> <span class="n">co</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">jena</span><span class="o">/</span><span class="n">trunk</span><span class="o">/</span><span class="n">jena</span><span class="o">-</span><span class="n">fuseki</span>
-</pre></div>
-
-
-<p>Build:</p>
-<div class="codehilite"><pre> <span class="n">mvn</span> <span class="n">clean</span> <span class="n">package</span>
-</pre></div>
-
-
-<p>This creates a standalone jar for the Fuseki server.</p>
-<div class="codehilite"><pre> <span class="n">target</span><span class="o">/</span><span class="n">fuseki</span><span class="o">-</span><span class="n">version</span><span class="o">-</span><span class="n">server</span><span class="p">.</span><span class="n">jar</span>
-</pre></div>
-
-
-<p>See the file <code>SETUP.txt</code> for working with Eclipse.</p>
</div>
</div>
Modified: websites/staging/jena/trunk/content/download/maven.html
==============================================================================
--- websites/staging/jena/trunk/content/download/maven.html (original)
+++ websites/staging/jena/trunk/content/download/maven.html Tue Sep 23 14:00:12 2014
@@ -241,9 +241,9 @@ to recent bug fixes, you should add the
<p>If you want you can checkout the Jena sources, build the artifacts and
install them in your local Maven repository, then you simply checkout the source
tree and build with maven
-<code>mvn install</code>. This assumes you have Maven and Subversion installed:</p>
-<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">jena</span><span class="o">/</span><span class="n">trunk</span><span class="o">/</span> <span class="n">Jena</span>
-<span class="n">cd</span> <span class="n">Jena</span>
+<code>mvn install</code>. This assumes you have Maven and Git installed:</p>
+<div class="codehilite"><pre><span class="n">git</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jena</span><span class="p">.</span><span class="n">git</span>
+<span class="n">cd</span> <span class="n">jena</span>
<span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span>
</pre></div>
Modified: websites/staging/jena/trunk/content/getting_involved/index.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_involved/index.html (original)
+++ websites/staging/jena/trunk/content/getting_involved/index.html Tue Sep 23 14:00:12 2014
@@ -171,37 +171,40 @@ CMS?</a> for guidance on how to do this.
<p>General help on how to use Jena with Maven is <a href="../download/maven.html">here</a>.</p>
<p>If you have problems with any of our SNAPSHOTs, let us know.</p>
<p>You can also check the state of each Jena module on our continuous integration server: <a href="https://builds.apache.org/view/G-L/view/Jena/">https://builds.apache.org/view/G-L/view/Jena/</a>.</p>
-<h3 id="subversion-repository">Subversion repository</h3>
-<p>You can find the Jena source code in the Apache subversion repository: <a href="http://svn.apache.org/repos/asf/jena/trunk/">http://svn.apache.org/repos/asf/jena/trunk/</a>.</p>
-<div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">jena</span><span class="o">/</span><span class="n">trunk</span><span class="o">/</span> <span class="n">Jena</span>
+<h3 id="git-repository">Git repository</h3>
+<p>You can find the Jena source code in the Apache git repository:
+<a href="https://git.apache.org/jena.git/">https://git.apache.org/jena.git/</a></p>
+<div class="codehilite"><pre><span class="n">git</span> <span class="n">clone</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">git</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">jena</span><span class="p">.</span><span class="n">git</span> <span class="n">Jena</span>
<span class="n">cd</span> <span class="n">Jena</span>
<span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span>
</pre></div>
+<p>There is also a read-only mirror on github:
+<a href="https://github.com/apache/jena/">https://github.com/apache/jena/</a></p>
<h3 id="open-issues">Open issues</h3>
<p>You can find a list of the <a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JENA+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide">open issues</a> on JIRA (sorted by priority) or the <a href="https://issues.apache.org/jira/browse/JENA#selectedTab=com.atlassian.jira.plugin.system.project%3Apopularissues-panel">popular issues</a> (sorted by votes).
Or, you can look at the <a href="https://issues.apache.org/jira/secure/QuickSearch.jspa?searchString=jena+updated:-1w">last week activity</a> to get a sense of what people are working on.</p>
<h3 id="submit-your-patches">Submit your patches</h3>
-<p>Patches should be attached to issues in Jira (click on <code>More Actions > Attach Files</code>).
-To create a patch you can simply use the command:</p>
-<div class="codehilite"><pre><span class="n">svn</span> <span class="n">diff</span> <span class="o">></span> <span class="n">JENA</span><span class="o">-</span><span class="n">XYZ</span><span class="p">.</span><span class="n">patch</span>
+<p>You can develop new contributions and work on patches using either the
+Apache-hosted git repsoitory of the mirror on github. Git pull requests
+made to the github mirror are routed back to the project.</p>
+<p>Alternatively, patches can be attached directly to issues in Jira
+(click on <code>More Actions > Attach Files</code>).</p>
+<p>Please, inspect your continution patch and make sure it includes all (and
+only) the relevant changes for a single issue. Don't forget tests!</p>
+<p>If you want to test if a patch applies cleanly you can use:</p>
+<div class="codehilite"><pre><span class="n">patch</span> <span class="o">-</span><span class="n">p0</span> <span class="o"><</span> <span class="n">JENA</span><span class="o">-</span><span class="n">XYZ</span><span class="p">.</span><span class="n">patch</span>
</pre></div>
-<p>Please, inspect your patch and make sure it includes all (and only) the relevant changes for a single issue. Don't forget tests!
-If you want to test if a patch applies cleanly you can use:</p>
-<div class="codehilite"><pre><span class="n">patch</span> <span class="o">-</span><span class="n">p0</span> <span class="o"><</span> <span class="n">JENA</span><span class="o">-</span><span class="n">XYZ</span><span class="p">.</span><span class="n">patch</span>
+<p>If you use Eclipse: right click on the project name in <code>Package Explorer</code>,
+select <code>Team > Create Patch</code> or <code>Team > Apply Patch</code>.</p>
+<p>You can also use git:</p>
+<div class="codehilite"><pre><span class="n">git</span> <span class="n">format</span><span class="o">-</span><span class="n">patch</span> <span class="n">origin</span><span class="o">/</span><span class="n">trunk</span>
</pre></div>
-<p>If you use Eclipse: right click on the project name in <code>Package Explorer</code>, select <code>Team > Create Patch</code> or <code>Team > Apply Patch</code>.</p>
-<h3 id="git-access-to-the-jena-source-code">Git access to the Jena source code</h3>
-<p>If you're more familiar with Git, you can use the Jena Git <strong>read-only</strong> mirrors
-listed at <a href="http://git.apache.org/">git.apache.org/</a>.</p>
-<p>Please note that git commits cannot be directly pulled back into the main
-svn repository. If you would like to contribute changes back to the Jena codebase, then please
-follow <a href="http://www.apache.org/dev/git.html#workflow">this workflow</a>.</p>
<h3 id="irc-channel">IRC channel</h3>
<p>Some Jena developers hang out on #jena on irc.freenode.net.</p>
<h3 id="how-apache-software-foundation-works">How Apache Software Foundation works</h3>
Modified: websites/staging/jena/trunk/content/help_and_support/bugs_and_suggestions.html
==============================================================================
--- websites/staging/jena/trunk/content/help_and_support/bugs_and_suggestions.html (original)
+++ websites/staging/jena/trunk/content/help_and_support/bugs_and_suggestions.html Tue Sep 23 14:00:12 2014
@@ -145,23 +145,15 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Reporting bugs and making suggestions</h1>
- <p>Please report bugs using ASF's <a href="https://issues.apache.org/jira/browse/JENA">JIRA instance for Jena</a>.
-General suggestions or requests for changes can also be discussed on the <a href="index.html">user list</a>,
+ <p>Please report bugs using ASF's <a href="https://issues.apache.org/jira/browse/JENA">JIRA instance for
+Jena</a>. General suggestions or
+requests for changes can also be discussed on the <a href="index.html">user list</a>,
but are less likely to be accidentally forgotten if you log them into JIRA.</p>
-<p>Patches and other code contributions should also be attached to issues in JIRA (click on <code>More Actions > Attach Files</code>).
-Please note that ASF requires that all contributions must be covered by an appropriate license.
-To create a patch you can simply use the command: </p>
-<div class="codehilite"><pre><span class="n">svn</span> <span class="n">diff</span> <span class="o">></span> <span class="n">JENA</span><span class="o">-</span><span class="n">XYZ</span><span class="p">.</span><span class="n">patch</span>
-</pre></div>
-
-
-<p>Please, inspect your patch and make sure it includes all (and only) the relevant changes for a single issue. Don't forget unit tests!
-If you want to test if a patch applies cleanly you can use: </p>
-<div class="codehilite"><pre><span class="n">patch</span> <span class="o">-</span><span class="n">p0</span> <span class="o"><</span> <span class="n">JENA</span><span class="o">-</span><span class="n">XYZ</span><span class="p">.</span><span class="n">patch</span>
-</pre></div>
-
-
-<p>If you use Eclipse: right click on the project name in <code>Package Explorer</code>, select <code>Team > Apply Patch</code>. </p>
+<p>Patches and other code contributions should also be attached to issues in
+JIRA (click on <code>More Actions > Attach Files</code>) or made via git pull requests.
+See '<a href="/getting_involved/">Getting Involved</a>'</p>
+<p>Please note that ASF requires that all contributions must be covered by an
+appropriate license.</p>
</div>
</div>