Repository: apex-site
Updated Branches:
  refs/heads/asf-site 1a9dad19e -> 9a6fe8c26


from cedfda71f7908cf704ae51d1e08cb54710ea13d5


Project: http://git-wip-us.apache.org/repos/asf/apex-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/apex-site/commit/9a6fe8c2
Tree: http://git-wip-us.apache.org/repos/asf/apex-site/tree/9a6fe8c2
Diff: http://git-wip-us.apache.org/repos/asf/apex-site/diff/9a6fe8c2

Branch: refs/heads/asf-site
Commit: 9a6fe8c2655e061711d2cf476a96bfff89c5933c
Parents: 1a9dad1
Author: Thomas Weise <[email protected]>
Authored: Wed Aug 31 14:11:36 2016 -0700
Committer: Thomas Weise <[email protected]>
Committed: Wed Aug 31 14:11:36 2016 -0700

----------------------------------------------------------------------
 content/contributing.html | 2 +-
 content/verification.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/apex-site/blob/9a6fe8c2/content/contributing.html
----------------------------------------------------------------------
diff --git a/content/contributing.html b/content/contributing.html
index 22a982f..28f52f7 100644
--- a/content/contributing.html
+++ b/content/contributing.html
@@ -112,7 +112,7 @@
 <li>Run <code>mvn license:format -Dlicense.skip=false</code> to automatically 
add the header when missing.</li>
 </ul>
 </li>
-<li>Once your feature is complete, submit the pull request on github against 
<code>master</code>.</li>
+<li>Once your feature is complete, submit the pull request on github against 
<code>master</code>. Use the JIRA number (e.g. APEXCORE-123) as prefix in the 
pull request title. This will ensure the information is attached to the JIRA 
ticket automatically.</li>
 <li>If you want specific people to review your pull request, use the 
<code>@</code> notation in Github comments to mention that user, and request 
that he/she reviews your changes.</li>
 <li>Check the status of the pull request and ensure the Travis CI build is 
successful. If not, inspect the linked build log for details.<ul>
 <li>If build fails due to license headers, follow instructions above.</li>

http://git-wip-us.apache.org/repos/asf/apex-site/blob/9a6fe8c2/content/verification.html
----------------------------------------------------------------------
diff --git a/content/verification.html b/content/verification.html
index c96c025..e3cca5b 100644
--- a/content/verification.html
+++ b/content/verification.html
@@ -127,10 +127,10 @@ The extracted directory should not contain any binary. 
Need to test this before
 </code></pre>
 <p>Please make sure no binary extension is listed here. Likely candidates are 
.jar files.  Additionally, for Malhar, demo package files, i.e. .apa files.</p>
 <h3 id="check-for-compilation-license-headers-etc-">Check for compilation, 
license headers, etc.</h3>
-<p>For Apex:</p>
+<p>For Apex Core:</p>
 <pre><code class="lang-bash">mvn clean apache-rat:check verify 
-Dlicense.skip=false install
 </code></pre>
-<p>For Malhar:</p>
+<p>For Apex Malhar:</p>
 <pre><code class="lang-bash">mvn clean apache-rat:check verify 
-Dlicense.skip=false -Pall-modules install
 </code></pre>
 <p>Jars should be installed in your maven repository, typically in 
<em>~/.m2/repository/org/apache/apex/</em> directory</p>

Reply via email to