Obviously a +1 for me. With regard to the plugin not supporting it, can’t Maven execute arbitrary Java/shell commands during build [1]? The issue on MINSTALL has been open since December 2012. I understand we might need a script wrapper to handle cross-platform functionality, but this might be easier/faster than waiting for MINSTALL team to fix it.
[1] http://stackoverflow.com/a/3493919/70465 Andy LoPresto [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Apr 13, 2016, at 6:33 PM, Matt Burgess <[email protected]> wrote: > > +1 > > >> On Apr 13, 2016, at 6:13 PM, Aldrin Piri <[email protected]> wrote: >> >> This was mentioned in the vote thread for the RC2 release and wanted to >> separate it out to keep the release messaging streamlined. As mentioned by >> Andy, the MD5 and SHA1 are subject to collisions. From another viewpoint, I >> like having this as part of the official release process as I typically >> generate this myself when updating the associated Homebrew formula with no >> real connection to the artifacts created other than me saying so. >> >> The drawback is that the Maven plugins that drives the release >> unfortunately does not support SHA-256.[1] As a result this would fall on >> the RM to do so but could easily be added to the documentation we have >> until the linked ticket is resolved. >> >> This vote will be a lazy consensus and remain open for 72 hours. >> >> >> [1] https://issues.apache.org/jira/browse/MINSTALL-82
signature.asc
Description: Message signed with OpenPGP using GPGMail
