yetus-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject yetus git commit: YETUS-406. Publish Yetus Audience Annotations to Maven Central
Date Thu, 26 Jul 2018 19:55:14 GMT
Repository: yetus
Updated Branches:
  refs/heads/master d3c4d1c50 -> 666b1192c

YETUS-406. Publish Yetus Audience Annotations to Maven Central

Signed-off-by: Sean Busbey <>


Branch: refs/heads/master
Commit: 666b1192c203d8e0e133d4b0a305158b34c66584
Parents: d3c4d1c
Author: Allen Wittenauer <>
Authored: Wed Jan 17 12:12:19 2018 -0800
Committer: Allen Wittenauer <>
Committed: Thu Jul 26 12:54:56 2018 -0700

 asf-site-src/source/contribute/ |  6 +++++-                                   | 26 ++++++++++++++++++-------
 2 files changed, 24 insertions(+), 8 deletions(-)
diff --git a/asf-site-src/source/contribute/ b/asf-site-src/source/contribute/
index 2200373..e7239e4 100644
--- a/asf-site-src/source/contribute/
+++ b/asf-site-src/source/contribute/
@@ -157,9 +157,10 @@ Both of these patch files should be uploaded to your release issue for
review. O
 Depending on how candidate evaluation goes, you may end up performing these steps multiple
times. Before you start, you'll need to decide when you want each candidate's vote thread
to end. ASF policy requires a minimum voting period of 72 hours (ref [ASF Voting Policy](,
so you should ensure enough padding to complete the candidate generation process in time.
Ideally, you would plan to post the vote thread on a Friday morning (US time) with a closing
date on Monday morning (US time).
 1. Update JIRA version release date. Browse to the JIRA project version management page (
and set the release date to when you expect your next vote thread to close. This date will
be used by our generated release notes.
+1. Update your `${HOME}/.m2/settings.xml` file to include the Maven snapshot information
as indicated on
 1. Build release artifacts. You should use our convenience script to create the tarballs
and markdown documents for a release. Run the following from the release staging branch and
inspect the results:
-        $ ./ --release
+        $ ./ --release --deploy
         $ ls -lah target/ target/ target/*.tar.gz
 1. Check out the staging area for release candidates and make a directory for this candidate,
somewhere outside of the your working directory. Copy the artifacts from the previous step
into place. For example, when working on RC1 for the 0.2.0 release
@@ -182,6 +183,7 @@ Depending on how candidate evaluation goes, you may end up performing
these step
         $ svn add 0.2.0-RC1
         $ svn commit -m "stage Apache Yetus 0.2.0-RC1"
 Afterwards, the artifacts should be visible via the web under the same URL used when checking
out. In the case of 0.2.0-RC1:
+1. Examine staged maven build. Go to the [ASF repository](
and log in with your asf LDAP credentials. Look for the staging repository with a name that
includes "yetus". Clicking on it will give you a link to an "Open" repository. You can examine
the structure in the Nexus API while you're logged in. If it looks essentially correct, "Close"
the repository. Refreshing and clicking on the repository will give you a link in the Summary
tab that other folks can use to interact with the repository.
 1. Call a vote on the release candidate. At this point you have everything you need to call
a vote. Your vote thread must contain "[VOTE]" in the subject line, a link to the candidate
staging area you created, a source repository commit hash, and voting rules. It should also
contain hashes for the artifacts. Here is an example draft for 0.2.0-RC1, update it as appropriate
for your release:
         Subject: [VOTE] Apache Yetus 0.2.0-RC1
@@ -197,6 +199,7 @@ Afterwards, the artifacts should be visible via the web under the same
URL used
         SHA512 (yetus-0.2.0-src.tar.gz) = e57b96533092356f3d5b9b4f47654fe9
         Source repository commit: 1e8f4588906a51317207092bd97b35687f2e3fa3
+        Maven staging repository:
         Our KEYS file is at:
         All artifacts are signed with my key (DEADBEEF)
@@ -484,6 +487,7 @@ It may take up to 24 hours for the artifacts to make their way to the
various mi
         Committed revision 1772.
 1. Resolve release issue; it should be marked as "fixed."
+1. Go to the [ASF repository]( and click 'Release' to put the
RC Maven artifacts into the release repository.
 1. Mark JIRA version as released. Browse to the [project version management page for the
YETUS JIRA tracker](
Mouse over the version you are managing, click on the gear in the far right, and select Release.
 1. Delete staging branch. Now that there is an immutable tag for the release, all commits
leading up to that release will be maintained by git. Should we need a future maintenance
release after this version, we can reestablish the branch based off of the release tag.
diff --git a/ b/
index 57920ed..a6f2dc9 100755
--- a/
+++ b/
@@ -19,6 +19,7 @@
 # create a more sustainable build system.
 # Pass --release to get release checks
+# Pass --deploy to deploy maven snapshot artifacts
 # Presumes you have
 #   * maven 3.2.0+
@@ -81,11 +82,17 @@ RAT_DOWNLOAD_URL=
 for arg in "$@"; do
-  if [ "--release" = "${arg}" ]; then
-    release=true
-  elif [ "--offline" = "${arg}" ]; then
-    offline=true
-  fi
+  case ${arg} in
+    --release)
+      release=true
+      ;;
+    --offline)
+      offline=true
+      ;;
+    --deploy)
+      deploy=true
+      ;;
+  esac
 echo "working on version '${YETUS_VERSION}'"
@@ -134,8 +141,13 @@ fi
 echo "running maven builds for java components"
 # build java components
-mvn "${MAVEN_ARGS[@]}" install --file yetus-project/pom.xml
-mvn "${MAVEN_ARGS[@]}" -Pinclude-jdiff-module install javadoc:aggregate --file audience-annotations-component/pom.xml
+if [[ "${deploy}" = true ]]; then
+  mvncmd=deploy
+  mvncmd=install
+mvn "${MAVEN_ARGS[@]}" "${mvncmd}" --file yetus-project/pom.xml
+mvn "${MAVEN_ARGS[@]}" -Pinclude-jdiff-module "${mvncmd}" javadoc:aggregate --file audience-annotations-component/pom.xml
 echo "building documentation"
 # build docs after javadocs

View raw message