yetus-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From a.@apache.org
Subject yetus git commit: YETUS-138. Skipping maven poms that don't package causes testing holes
Date Sun, 01 Nov 2015 19:37:13 GMT
Repository: yetus
Updated Branches:
  refs/heads/asf-site f7e1368c8 -> ce16aba54


YETUS-138. Skipping maven poms that don't package causes testing holes


Project: http://git-wip-us.apache.org/repos/asf/yetus/repo
Commit: http://git-wip-us.apache.org/repos/asf/yetus/commit/ce16aba5
Tree: http://git-wip-us.apache.org/repos/asf/yetus/tree/ce16aba5
Diff: http://git-wip-us.apache.org/repos/asf/yetus/diff/ce16aba5

Branch: refs/heads/asf-site
Commit: ce16aba5431193a1d1f46a0e8f7d4761e42a8b91
Parents: f7e1368
Author: Allen Wittenauer <aw@apache.org>
Authored: Sun Nov 1 11:37:06 2015 -0800
Committer: Allen Wittenauer <aw@apache.org>
Committed: Sun Nov 1 11:37:06 2015 -0800

----------------------------------------------------------------------
 documentation/latest/precommit-advanced/index.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/yetus/blob/ce16aba5/documentation/latest/precommit-advanced/index.html
----------------------------------------------------------------------
diff --git a/documentation/latest/precommit-advanced/index.html b/documentation/latest/precommit-advanced/index.html
index 2cccba1..da0f4da 100644
--- a/documentation/latest/precommit-advanced/index.html
+++ b/documentation/latest/precommit-advanced/index.html
@@ -326,8 +326,7 @@
 <li><p>BUILD_NATIVE will be set to true if the system has requested that non-JVM-based
code be built (e.g., JNI or other compiled C code). Under Jenkins, this is always true.</p></li>
 <li><p>BUILDTOOL specifies which tool is currently being used to drive compilation.
 Additionally, many build tools define xyz_ARGS to pass on to the build tool command line.
(e.g., MAVEN_ARGS if maven is in use).  Projects may set this in their personality.  NOTE:
today, only one build tool at a time is supported.  This may change in the future.</p></li>
 <li><p>CHANGED_FILES is a list of all files that appear to be added, deleted,
or modified in the patch.</p></li>
-<li><p>CHANGED_UNFILTERED_MODULES is a list of all modules that house all of
the CHANGED_FILES.  Be aware that the root of the source tree is reported as &rsquo;.&rsquo;.</p></li>
-<li><p>CHANGED_MODULES reports which modules that appear to have source code
in them.</p></li>
+<li><p>CHANGED_MODULES is a list of all modules that house all of the CHANGED_FILES.
 Be aware that the root of the source tree is reported as &rsquo;.&rsquo;.</p></li>
 <li><p>GITHUB_REPO is to help test-patch when talking to Github.  If test-patch
is given just a number on the command line, it will default to using this repo to determine
the pull request.</p></li>
 <li><p>HOW_TO_CONTRIBUTE should be a URL that points to a project&rsquo;s
on-boarding documentation for new users. Currently, it is used to suggest a review of patch
naming guidelines. Since this should be project specific information, it is useful to set
in a project&rsquo;s personality.</p></li>
 <li><p>JIRA_ISSUE_RE is to help test-patch when talking to JIRA.  It helps determine
if the given project is appropriate for the given JIRA issue.</p></li>


Mime
View raw message