[
https://jira.jboss.org/jira/browse/JBIDE-3675?page=com.atlassian.jira.plu...
]
Nick Boldt updated JBIDE-3675:
------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Crap. We need Ant 1.7 for this and there's no guarantee that any given hudson box as
1.7 installed. Reverting w/ TODO markers for later.
make md5sum files easier to use
-------------------------------
Key: JBIDE-3675
URL:
https://jira.jboss.org/jira/browse/JBIDE-3675
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.0.0.GA
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Minor
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The current *.zip.MD5 files contain ONLY the m5dsum, and no EOL character.
8414b9bcdb4ed46639e4fa3d9f36731e
So, to check a sum, users must do this:
$ md5sum JBossTools-ALL-linux-gtk-3.0.0.CR2-R200901280154.zip
8414b9bcdb4ed46639e4fa3d9f36731e JBossTools-ALL-linux-gtk-3.0.0.CR2-R200901280154.zip
then manually compare the generated hash with the published one.
If they contained both the hash and the filename, then users could run this:
$ cat JBossTools-ALL-linux-gtk-3.0.0.CR2-R200901280154.zip.MD5
8414b9bcdb4ed46639e4fa3d9f36731e JBossTools-ALL-linux-gtk-3.0.0.CR2-R200901280154.zip
$ md5sum -c JBossTools-ALL-linux-gtk-3.0.0.CR2-R200901280154.zip.MD5
JBossTools-ALL-linux-gtk-3.0.0.CR2-R200901280154.zip: OK
and would know immediately if the hash matched, without having to manually diff them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira