I'm -1 to making a new format, but ambivalent about changing it to
match openssl standards
--Brian (mobile)
On Jan 2, 2009, at 5:31 AM, Benjamin Bentmann
<[email protected]> wrote:
Hi,
With regard to MINSTALL-47, I would like to discuss if we can/should
change the format used for checksum files generated by Maven.
Currently, Maven outputs the plain checksum as-is to the checksum
file (cf. [1]), e.g.
1dbbdec30feca97198d5d7e96d42dc57
In the mentioned issue, it was requested to append the filename,
separated by a space and asterisk, to the checksum:
1dbbdec30feca97198d5d7e96d42dc57 *maven-metadata.xml
My naive assumption is that any decent checksum verification tool
out there is able to strip extraneous characters from the checksum
file if not processed. In contrast, guessing missing bits is usually
harder for tools. So I believe changing the checksum format as
requested would increase tool support.
Maven itself can already process this checksum format (due to
MNG-797) and an IT is online (for MNG-1349 which merely requires
newer Maven versions for SHA-1 checksums in OpenSSL format).
Technically, this change would affect the Maven Install Plugin and
the DefaultWagonManager from maven-artifact-manager (aka maven-
compat).
WDYT?
Benjamin
[0] http://jira.codehaus.org/browse/MINSTALL-47
[1]
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml.md5
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
