On 29/05/2020 13:05, Mark Thomas wrote:
> Hi,
> 
> Currently we use the (very old) Maven Ant Tasks to upload files to
> Nexus. This has a hard-coded feature that adds MD5 and SHA-1 hashes for
> every uploaded file. It also adds hashes for .asc files.
> 
> I investigated manually adding .sha256 and .sha512 files. This works, bu
> the upload process still adds .md5 and .sha1 files for the .sha256 and
> .sha512 files. This is workable but not ideal.
> 
> I am currently investigating the possibility of switching to the newer
> Maven Resolver Ant Tasks. This is a work in progress. It has a LOT more
> dependencies and the default behaviour is unchanged. I am currently
> looking at the source to see if the behaviour could be configured.
> 
> In amongst all of this I had a thought. What if we just made a binary
> patch to the Maven Ant Tasks to switch it from creating MD5 and SHA-1
> hashes to creating SHA-256 and SHA-512 hashes? At first glance this
> looks to be a small tweak to a single class that should be doable with
> BCEL (a bit like a very targetted Jakarta Migration Tool). Is this a
> terrible idea? I wanted to get some feedback on this while I continued
> to look at the Maven Resolver Ant Tasks.

A little more information with a summary.

Maven Ant Tasks
 - single JAR
 - creates hashes for .asc, sha256 and sha512 files if added manually
 - hard coded to MD5 and SHA-1
 - relevant code is ALv2 licensed (and ASF owned) so modification is
   trivial

Maven Resolver Ant Tasks
 - multiple (10s?) JARs
 - doesn't create hashes for .asc files (by default)
 - creates hashes for sha256 and sha512 files if added manually
 - hard coded to MD5 and SHA-1
 - relevant code (Eclipse Aether) is EPL 1.0 licensed which makes it
   category B and therefore trickier for us to modify

Both approaches are either deprecated /retired or depend on deprecated /
retired components.

I'm continuing to look for other options. Next up the Nexus Staging Ant
Tasks.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to