On Tue, 07 Aug 2018 23:29:04 +0200, wrote:
squashed and kept only SHA-512
Maven core plugins don't cover everything even quite generic like
creating checksums, that's why there are many Maven plugins out there...
Maven Resolver generates these files while deploying, so for us there was
squashed and kept only SHA-512
Maven core plugins don't cover everything even quite generic like creating
checksums, that's why there are many Maven plugins out there...
Regards,
Hervé
- Mail original -
De: "Michael Osipov"
À: "Maven Developers List" , "herve boutemy"
Cc:
Am 2018-08-07 um 22:50 schrieb herve.bout...@free.fr:
Hi,
Recently, Apache distribution policy changed regarding checksums [1]: now,
SHA-256 or SHA-512 checksums are required.
This lead to discussion about changing checksums used on Maven repository
and/or Apache Nexus repository.
But Maven
Hi,
Recently, Apache distribution policy changed regarding checksums [1]: now,
SHA-256 or SHA-512 checksums are required.
This lead to discussion about changing checksums used on Maven repository
and/or Apache Nexus repository.
But Maven repository requirements and Apache source distribution
Hi,
we have a number of Maven Jobs:
https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/
which are superflous in the meantime cause they are handled by the
pipelines.
I would go to delete them on 17.08.2018 except somebody will object?
Kind regards
Karl Heinz Marbaise
Related to Incremental - idempotent builds would be good.
Having been exposed to Google's Blaze (now Bazel in OSSland) and directed
graph build system science (as opposed to recursive build systems) there's
a great efficiency from skipping parts of a build that don't need to be
done.
Also
Hi Max,
regarding the contribution, I would like to propose the following:
- At least create a JIRA issue for every feature.
- Due to the large amount of code I can imagine there are some
dependencies between the features, i.e some features should be implemented
first.
- Based on that we can
Thanks Robert, I did suspect that it was something to do with the way the
unit test runs was not simulating the phase. I set up a simple test project
using the snapshot of my plugin, and it works as designed, so I'm going to
take that test out and assume that it 'just works'.
Cheers,
KEv.
On
Hi Robert ,
*JDK 11 Early Access build 25 is available at : - **jdk.java.net/11/*
* *JDK 11 entered Rampdown Phase 2 on 26-July [1]*
o The overall feature set is frozen. No further JEPs will be
targeted to this release.
o We now turn our focus to P1 and P2 bugs.
* Release
