tinkerpop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From spmalle...@apache.org
Subject svn commit: r1717966 - /incubator/tinkerpop/site/docs/3.1.1-SNAPSHOT/dev/developer/index.html
Date Fri, 04 Dec 2015 14:06:04 GMT
Author: spmallette
Date: Fri Dec  4 14:06:04 2015
New Revision: 1717966

URL: http://svn.apache.org/viewvc?rev=1717966&view=rev
Add "logging" section to tinkerpop dev docs.


Modified: incubator/tinkerpop/site/docs/3.1.1-SNAPSHOT/dev/developer/index.html
URL: http://svn.apache.org/viewvc/incubator/tinkerpop/site/docs/3.1.1-SNAPSHOT/dev/developer/index.html?rev=1717966&r1=1717965&r2=1717966&view=diff
--- incubator/tinkerpop/site/docs/3.1.1-SNAPSHOT/dev/developer/index.html (original)
+++ incubator/tinkerpop/site/docs/3.1.1-SNAPSHOT/dev/developer/index.html Fri Dec  4 14:06:04
@@ -828,6 +828,7 @@ span.line-numbers { border-right: 1px so
 <li><a href="#documentation">Documentation</a></li>
+<li><a href="#logging">Logging</a></li>
@@ -881,7 +882,7 @@ license and warrant that you have the le
 <div class="paragraph">
 <p>New contributors can start development with TinkerPop by first <a href="https://help.github.com/articles/fork-a-repo/">forking
 then cloning</a> the Apache TinkerPop <a href="https://github.com/apache/incubator-tinkerpop">GitHub
repository</a>. Generally
-speaking it is best to tie any work done to an issue in <a href="https://issues.apache.org/jira/browse/TINKERPOP3">JIRA</a>.
+speaking it is best to tie any work done to an issue in <a href="https://issues.apache.org/jira/browse/TINKERPOP">JIRA</a>.
 Either scan through JIRA for an existing open issue to work on or create a new one.</p>
 <div class="admonitionblock note">
@@ -1151,7 +1152,7 @@ tags, as they produce permanent clutter.
 <div class="sect2">
 <h3 id="_issue_tracker_conventions">Issue Tracker Conventions</h3>
 <div class="paragraph">
-<p>TinkerPop uses Apache JIRA as its <a href="https://issues.apache.org/jira/browse/TINKERPOP3">issue
tracker</a>.  JIRA is a
+<p>TinkerPop uses Apache JIRA as its <a href="https://issues.apache.org/jira/browse/TINKERPOP">issue
tracker</a>.  JIRA is a
 very robust piece of software with many options and configurations.  To simplify usage and
ensure consistency across
 issues, the following conventions should be adhered to:</p>
@@ -1249,7 +1250,7 @@ replaced then the comment can simply rea
-<p><code>@see &lt;a href="https://issues.apache.org/jira/browse/TINKERPOP3-XXX"&gt;TINKERPOP3-XXX&lt;/a&gt;</code>
- supply a link to the
+<p><code>@see &lt;a href="https://issues.apache.org/jira/browse/TINKERPOP-XXX"&gt;TINKERPOP-XXX&lt;/a&gt;</code>
- supply a link to the
 JIRA issue for reference.</p>
@@ -1661,6 +1662,17 @@ uploaded to the server and should preser
+<div class="sect2">
+<h3 id="logging">Logging</h3>
+<div class="paragraph">
+<p>TinkerPop uses SLF4j for logging and typically leans back on Log4j as the implementation.
Configuring log outputs
+for debugging purposes within tests can be altered by editing the <code>log4j-test.properties</code>
file in each module&#8217;s test
+resources.  That file gets copied to the <code>target/test-classes</code> on
build and surefire and failsafe plugins in maven
+are then configured to point at that area of the file system for those configuration files.
The properties files
+can be edited to fine tune control of the log output, but generally speaking the current
configuration is likely
+best for everyone&#8217;s general purposes, so if changes are made please revert them
prior to commit.</p>
 <h1 id="_release_process" class="sect0">Release Process</h1>
@@ -1915,7 +1927,7 @@ handled document generation and this ste
 <p><code>mvn deploy -Papache-release -DcreateChecksum=true -Dmaven.test.skip=true</code>
- deploy signed artifacts with checksums to <a href="https://repository.apache.org/">Apache
Nexus</a>. Review (artifacts versions, file sizes, anything that might be out of place
- request another committer to review as well) but do NOT close/release the staging repository
at this time.</p>
-<p>Review generated artifacts to be sure they have both javadocs and asciidocs present</p>
+<p>Review generated artifacts to be sure they have both javadocs and asciidocs present
then "close" the repo - if the repo is left open it will be automatically dropped after five
days and closing the repo will allow it to stay available for a full ninety days which is
more than enough time to complete a vote.</p>
 <p>Upload artifacts to <code>https://dist.apache.org/repos/dist/dev/incubator/tinkerpop</code>
for <code>[VOTE]</code> review.</p>
@@ -1991,7 +2003,7 @@ handled document generation and this ste
-<p>Submit for <code>[VOTE]</code> at <code>dev@tinkerpop.incubator.apache.org</code>
(see email template below)</p>
+<p>Submit for <code>[VOTE]</code> at <code>dev@tinkerpop.apache.org</code>
(see email template below)</p>
 <p><strong>Wait for vote acceptance</strong> (72 hours)</p>
@@ -2013,7 +2025,7 @@ handled document generation and this ste
 <div class="olist loweralpha">
 <ol class="loweralpha" type="a">
-<p>Include the vote tally: "Apache TinkerPop (<a href="http://tinkerpop.incubator.apache.org/">http://tinkerpop.incubator.apache.org/</a>)
would like to release TinkerPop 3.1.1-SNAPSHOT. We had a dev@ VOTE which resulted in a tally
of +1 (3), 0 (0), and -1 (0). We now present our artifacts for vote by Incubator."</p>
+<p>Include the vote tally: "Apache TinkerPop (<a href="http://tinkerpop.apache.org/">http://tinkerpop.apache.org/</a>)
would like to release TinkerPop 3.1.1-SNAPSHOT. We had a dev@ VOTE which resulted in a tally
of +1 (3), 0 (0), and -1 (0). We now present our artifacts for vote by Incubator."</p>
@@ -2043,6 +2055,9 @@ handled document generation and this ste
 <p><code>cd release; svn add 3.1.1-SNAPSHOT/; svn ci -m "TinkerPop 3.1.1-SNAPSHOT
+<p>If there is are releases present in SVN that represents lines of code that are no
longer under development, then remove those releases. In other words, if <code>3.1.0-incubating</code>
is present and <code>3.1.1-incubating</code> is released then remove <code>3.1.0-incubating</code>.
 However, if <code>3.0.2-incubating</code> is present and that line of code is
still under potential development, it may stay.</p>
 <p>Update homepage with references to latest distribution and to other internal links
elsewhere on the page.</p>
@@ -2073,10 +2088,10 @@ Two binary distributions are provided fo
 The online docs can be found here:
-	http://tinkerpop.incubator.apache.org/docs/3.1.1-SNAPSHOT/ (user docs)
-	http://tinkerpop.incubator.apache.org/docs/3.1.1-SNAPSHOT/upgrade.html (upgrade docs)
-	http://tinkerpop.incubator.apache.org/javadocs/3.1.1-SNAPSHOT/core/ (core javadoc)
-	http://tinkerpop.incubator.apache.org/javadocs/3.1.1-SNAPSHOT/full/ (full javadoc)
+	http://tinkerpop.apache.org/docs/3.1.1-SNAPSHOT/ (user docs)
+	http://tinkerpop.apache.org/docs/3.1.1-SNAPSHOT/upgrade.html (upgrade docs)
+	http://tinkerpop.apache.org/javadocs/3.1.1-SNAPSHOT/core/ (core javadoc)
+	http://tinkerpop.apache.org/javadocs/3.1.1-SNAPSHOT/full/ (full javadoc)
 The tag in Apache Git can be found here:
@@ -2128,7 +2143,7 @@ committed.  You will probably find that
 Of course, you can decline and instead remain as a contributor, participating as you do now.
 A. This personal invitation is a chance for you to accept or decline in private.  Either
way, please let us know in
-reply to the private@tinkerpop.incubator.apache.org address only.
+reply to the private@tinkerpop.apache.org address only.
 B. If you are accepting, the next step is to register an iCLA with the Apache Software Foundation:
     1. Details of the iCLA and the forms are found through this link: http://www.apache.org/licenses/#clas.
@@ -2870,7 +2885,7 @@ roadmap:</p>
 <div id="footer">
 <div id="footer-text">
-Last updated 2015-11-23 17:11:52 -05:00
+Last updated 2015-12-04 09:04:36 -05:00

View raw message