Modify

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#11325 closed enhancement (wontfix)

Provide jar checksum in status report

Reported by: naoliv Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: Cc:

Description

JOSM should also include in its status report a checksum/hash (MD5, SHA1 or other) of the jar file, if possible.
This would allow the developers to see if the file differs from the official one (for example, in #11300 it could be used to see if users are really using the latest JOSM release or if their jar has been modified/corrupted).

Attachments (0)

Change History (3)

comment:1 Changed 8 years ago by stoecker

Resolution: wontfix
Status: newclosed

Happens to seldom to be necessary.

comment:2 Changed 8 years ago by naoliv

But it won't hurt to have this...

comment:3 in reply to:  2 Changed 8 years ago by stoecker

Replying to naoliv:

But it won't hurt to have this...

Well, that's not so easy. First we provide download options to strip certain parts of the jar (e.g. the signatures or the language files). Second debian and others do their own builds. And third calculating the checksum is not that trivial, as it requires access to the system which may not always be easy (i.e. webstart). So a lot of trouble and only little benefit... :-)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.