[
https://issues.apache.org/jira/browse/OOZIE-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399404#comment-16399404
]
Robert Kanter commented on OOZIE-3189:
--------------------------------------
The 002 patch replaces the {{releaseVersion}} resolution with:
{noformat}
xmllint --xpath "//*[local-name()='project']/*[local-name()='version']/text()"
pom.xml
{noformat}
This is much faster as it doesn't have to run {{mvn}}, nor download any
dependencies if you don't have them (e.g. a clean local maven repo). It simply
parses the XML.
AFAIK, {{xmllint}} should normally be installed. If we don't want to replace
this with a non-maven command, we could instead use:
{noformat}
mvn -q -Dexec.executable="echo" -Dexec.args='${project.version}'
--non-recursive exec:exec
{noformat}
This avoids having to grep out any of the other stuff.
Both of these came from
https://stackoverflow.com/questions/3545292/how-to-get-maven-project-version-to-the-bash-command-line
> Update the release script and wiki page to use sha512 instead of md5
> --------------------------------------------------------------------
>
> Key: OOZIE-3189
> URL: https://issues.apache.org/jira/browse/OOZIE-3189
> Project: Oozie
> Issue Type: Improvement
> Components: scripts
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Blocker
> Fix For: 5.0.0
>
> Attachments: OOZIE-3189.001.patch, OOZIE-3189.002.patch
>
>
> Apache has updated it's policy on the release signatures, as per it's website
> [here|https://www.apache.org/dev/release-distribution#sigs-and-sums] and a
> recent email. Basically, all future releases should be providing a sha512
> checksum instead of an md5 one.
> There are two tasks:
> # Update the release script to use sha512 instead of md5
> [https://github.com/apache/oozie/blob/master/bin/create-release-artifact#L71]
> [https://www.apache.org/dev/release-signing#sha-checksum]
> # Update the wiki (requires committer/pmc permissions?)
> [https://cwiki.apache.org/confluence/display/OOZIE/How+To+Release]
> While we're updating the wiki, we should add details on:
> # Making sure the gpg key used for signing releases is 4096 bit RSA
> # Publishing your gpg public key to a key server
> ([https://www.apache.org/dev/release-signing#keyserver])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
