You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "adoroszlai (via GitHub)" <gi...@apache.org> on 2025/01/06 11:31:37 UTC

Re: [PR] HDDS-11925. Fix deploy step in Release Manager guide [ozone-site]

adoroszlai commented on PR #109:
URL: https://github.com/apache/ozone-site/pull/109#issuecomment-2572923357

   Updated the PR:
   
   - Steps now include two separate builds, same as previously:
      1. `mvn clean install` to fetch dependencies and ensure that the build is successful
      2. `mvn deploy`, like originally, to produce the artifacts that get published.  Added `-DdeployAtEnd=true` to avoid partial build getting deployed.
   - The key difference is that tarballs are copied from the second build, not the first one.  This ensures jars in the tarball are the same as those published to Maven.
   - Moved initial setup (Maven configuration) to Prerequisites.
   - Also moved comment about GNU vs. BSD tar to Prerequisites.
   - Split pre-build `rat` check to new section "Sanity Checks", which can be expanded later if needed.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org