On 19/10/2023 03:17, Christopher Schultz wrote:
But Mark, if you missed my message from the 13th, you'll see that the
problem is I'm running a slightly different version of Java than you
are, and the exact spelling of the version string is causing the problem
-- mostly in MANIFEST.MF files
Le 19/10/2023 à 04:17, Christopher Schultz a écrit :
But Mark, if you missed my message from the 13th, you'll see that the
problem is I'm running a slightly different version of Java than you
are, and the exact spelling of the version string is causing the problem
-- mostly in MANIFEST.MF
Mark,
On 10/18/23 11:43, Mark Thomas wrote:
On 18/10/2023 15:06, Konstantin Kolinko wrote:
ср, 18 окт. 2023 г. в 14:55, Mark Thomas :
On 17/10/2023 16:36, Mark Thomas wrote:
It looks like Javadoc generation is different between Linux and Windows
with Java 21. That is still causing issues
On 18/10/2023 16:43, Mark Thomas wrote:
On 18/10/2023 15:06, Konstantin Kolinko wrote:
ср, 18 окт. 2023 г. в 14:55, Mark Thomas :
On 17/10/2023 16:36, Mark Thomas wrote:
It looks like Javadoc generation is different between Linux and Windows
with Java 21. That is still causing issues for
On 18/10/2023 15:06, Konstantin Kolinko wrote:
ср, 18 окт. 2023 г. в 14:55, Mark Thomas :
On 17/10/2023 16:36, Mark Thomas wrote:
It looks like Javadoc generation is different between Linux and Windows
with Java 21. That is still causing issues for the full-docs package for
Tomcat 11. I'm
ср, 18 окт. 2023 г. в 14:55, Mark Thomas :
>
> On 17/10/2023 16:36, Mark Thomas wrote:
>
> > It looks like Javadoc generation is different between Linux and Windows
> > with Java 21. That is still causing issues for the full-docs package for
> > Tomcat 11. I'm still looking into options for fixing
On 17/10/2023 16:36, Mark Thomas wrote:
It looks like Javadoc generation is different between Linux and Windows
with Java 21. That is still causing issues for the full-docs package for
Tomcat 11. I'm still looking into options for fixing that. Other than
that, I'm not seeing any
I've fixed a couple of issues that were breaking reproducibility for
some files. I'll back-port those as soon as I have sent this mail.
It looks like Javadoc generation is different between Linux and Windows
with Java 21. That is still causing issues for the full-docs package for
Tomcat 11.
Emmanuel,
On 10/12/23 18:13, Emmanuel Bourg wrote:
Le 12/10/2023 à 23:27, Christopher Schultz a écrit :
I installed the ZIP version of Temurin Java 21 to match your release
toolchain and I get every file being different. But the versions are
not exactly the same, so that may be the reason:
Le 12/10/2023 à 23:27, Christopher Schultz a écrit :
I installed the ZIP version of Temurin Java 21 to match your release
toolchain and I get every file being different. But the versions are not
exactly the same, so that may be the reason:
Release Java: 21+25-2513
Local Java: 21+35-LTS
Mark,
On 10/12/23 15:50, Christopher Schultz wrote:
Mark,
On 10/12/23 13:15, Mark Thomas wrote:
12 Oct 2023 10:29:02 Christopher Schultz :
All,
I've been working on an "ant verify-release" target and I'm finding
that in the 9.0 release -- the one I'm using as a guinea pig -- the
SHA-512
Mark,
On 10/12/23 13:15, Mark Thomas wrote:
12 Oct 2023 10:29:02 Christopher Schultz :
All,
I've been working on an "ant verify-release" target and I'm finding
that in the 9.0 release -- the one I'm using as a guinea pig -- the
SHA-512 hashes do not match for these artifacts:
12 Oct 2023 10:29:02 Christopher Schultz :
All,
I've been working on an "ant verify-release" target and I'm finding
that in the 9.0 release -- the one I'm using as a guinea pig -- the
SHA-512 hashes do not match for these artifacts:
apache-tomcat-9.0.82-fulldocs.tar.gz
13 matches
Mail list logo
