On Thu, 20 Aug 2020 at 23:23, Gilles Sadowski wrote:
>
> Le jeu. 20 août 2020 à 23:15, sebb a écrit :
> >
> > On Thu, 20 Aug 2020 at 21:54, Gilles Sadowski wrote:
> > >
> > > Le jeu. 20 août 2020 à 22:00, sebb a écrit :
> > > >
> > > > AFAICT the release artifacts have only sha512 files.
> > >
Le jeu. 20 août 2020 à 23:15, sebb a écrit :
>
> On Thu, 20 Aug 2020 at 21:54, Gilles Sadowski wrote:
> >
> > Le jeu. 20 août 2020 à 22:00, sebb a écrit :
> > >
> > > AFAICT the release artifacts have only sha512 files.
> > >
> > > However the Maven jars have md5 and sha1; I don't think there's
+1
On Tue, 18 Aug 2020 at 07:38, Romain Manni-Bucau wrote:
>
> Always sad of this artifact renaming thing when there is only minor
> breaking changes - or none for most artifacts - but works as expected on my
> test apps and source artifact looks good, so:
>
> [X] +1 Release these artifacts
>
>
On Thu, 20 Aug 2020 at 21:54, Gilles Sadowski wrote:
>
> Le jeu. 20 août 2020 à 22:00, sebb a écrit :
> >
> > AFAICT the release artifacts have only sha512 files.
> >
> > However the Maven jars have md5 and sha1; I don't think there's much
> > we can do about that.
> > This is due to Nexus
Le jeu. 20 août 2020 à 22:00, sebb a écrit :
>
> AFAICT the release artifacts have only sha512 files.
>
> However the Maven jars have md5 and sha1; I don't think there's much
> we can do about that.
> This is due to Nexus and/or Maven.
>
> The hash types look OK to me.
>
> Anyway the release
AFAICT the release artifacts have only sha512 files.
However the Maven jars have md5 and sha1; I don't think there's much
we can do about that.
This is due to Nexus and/or Maven.
The hash types look OK to me.
Anyway the release distribution page [1] does not relate to Maven
releases AFAIK.
On
On Thu, Aug 20, 2020 at 1:24 PM Gilles Sadowski
wrote:
> Hi Thomas.
>
> Le jeu. 20 août 2020 à 09:14, Thomas Vandahl a écrit :
> >
> > Could I please ask for one more PMC vote?
>
> IIUC[1], this release should not ship with SHA1 or MD5 files.
>
Correct. ONLY SHA-256 or 512.
Gary
> Regards,
Hi Thomas.
Le jeu. 20 août 2020 à 09:14, Thomas Vandahl a écrit :
>
> Could I please ask for one more PMC vote?
IIUC[1], this release should not ship with SHA1 or MD5 files.
Regards,
Gilles
[1] https://infra.apache.org/release-distribution.html#sigs-and-sums
>
> TIA
> Bye, Thomas
>
> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear all,
could someone please have a look at my PR for Commons Configuration?
https://github.com/apache/commons-configuration/pull/45
Thank you in advance
Oliver
- --
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin,
On Thu, Aug 20, 2020 at 7:57 AM Peter Lee wrote:
> Hi all,
>
> The builds in jenkins and github actions are failing.
> For jenkins, the java7, 14 and 16 builds are failing. As we have moved
> from JAVA 7 to 8, maybe we should disable java 7 build in jenkins? Besides
> the java 14 and 16 are also
Hello.
Le jeu. 20 août 2020 à 13:56, Peter Lee a écrit :
>
> Hi all,
>
> The builds in jenkins and github actions are failing.
> For jenkins, the java7, 14 and 16 builds are failing. As we have moved from
> JAVA 7 to 8, maybe we should disable java 7 build in jenkins?
+1
Gilles
> Besides the
Hi all,
The builds in jenkins and github actions are failing.
For jenkins, the java7, 14 and 16 builds are failing. As we have moved from
JAVA 7 to 8, maybe we should disable java 7 build in jenkins? Besides the java
14 and 16 are also failing, and we can have some "allow failure" config on
Could I please ask for one more PMC vote?
TIA
Bye, Thomas
On 17.08.20 08:29, Thomas Vandahl wrote:
> This has been a major overhaul of JCS with many adjustments for JDK 8+,
> better concurrency and logging. Finally, I would like to
> release Apache Commons JCS 3.0.
[...]
> Please review the
13 matches
Mail list logo