+1
Thank you.
Regards,
Marat Abrarov.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Alright, thanks! I know what to do now. Will work on this next week and
let you know. Thank you very much again for your support!
Am 2020-09-27 um 00:14 schrieb Dan Tran:
without -Daether.checksums.algorithms=SHA1,MD5, very slow
-D
On Sat, Sep 26, 2020 at 3:11 PM Michael Osipov wrote:
without -Daether.checksums.algorithms=SHA1,MD5, very slow
-D
On Sat, Sep 26, 2020 at 3:11 PM Michael Osipov wrote:
> Awesome, what about with the fix, but with the default list of hashing
> algos (SHA-512, SHA-256, SHA-1, MD5) in place?
>
> Am 2020-09-27 um 00:07 schrieb Dan Tran:
> > it
Awesome, what about with the fix, but with the default list of hashing
algos (SHA-512, SHA-256, SHA-1, MD5) in place?
Am 2020-09-27 um 00:07 schrieb Dan Tran:
it works using the provided commitID +
-Daether.checksums.algorithms=SHA1,MD5
-D
On Sat, Sep 26, 2020 at 2:25 PM Michael Osipov
it works using the provided commitID +
-Daether.checksums.algorithms=SHA1,MD5
-D
On Sat, Sep 26, 2020 at 2:25 PM Michael Osipov wrote:
> Gosh, I assumed so. Every SHA family is horrible in terms of
> performance. This is going to be a huge problem for the community, I
> would prefer Blake2
Gosh, I assumed so. Every SHA family is horrible in terms of
performance. This is going to be a huge problem for the community, I
would prefer Blake2 or Blake3 for this.
Anyway, I think this is the root cause, actually the fix:
Hi,
We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422=12346511=Text
There are still a couple of issues left in JIRA:
I am able to pin down the problematic commit:
https://github.com/apache/maven-resolver/commit/8e8a4f1944a0589397e36a5dd049ec765424e863
Adding -Daether.checksums.algorithms=SHA1,MD5 to maven command line does
not help
Sorry about the delay
-D
On Wed, Sep 16, 2020 at 1:57 AM Michael Osipov
Am 2020-09-20 um 20:38 schrieb Robert Scholte:
With the next release of Maven the current maven-gpg-plugin will become useless.
With the build//consumer pom, the local pom will be different compared to the
uploaded pom.
However, the maven-gpg-plugin now uses the pom.xml of the local project.
Ok, I don't want to reinvent the wheels, so
How to reach handle to project artifacts list, especially project pom after
transformation in plugin code?
Some plugin examples, point which component should I use to achieve this
will be great.
pt., 25 wrz 2020 o 17:05 Robert Scholte napisał(a):
>
hboutemy merged pull request #201:
URL: https://github.com/apache/maven-site/pull/201
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
11 matches
Mail list logo
