Thank you so much for your help.
I will have more questions tomorrow once I start working on the Jira Issue
that I have selected
On Tue, Dec 12, 2023 at 2:59 PM Gary Gregory wrote:
> The simplest would to add a comment to the Jira ticket.
>
> Gary
>
> On Tue, Dec 12, 2023, 2:55 PM Charles
The simplest would to add a comment to the Jira ticket.
Gary
On Tue, Dec 12, 2023, 2:55 PM Charles Stockman
wrote:
> Thanks for your answers. What is the best practice for letting people know
> you working an issue so they do not duplicate effort.
>
> On Tue, Dec 12, 2023 at 2:50 PM Gary
Thanks for your answers. What is the best practice for letting people know
you working an issue so they do not duplicate effort.
On Tue, Dec 12, 2023 at 2:50 PM Gary Gregory wrote:
> Hi Charles,
>
> Implementing (1) would cause an infinite loop of builds since the file thw
> build would update
Hi Charles,
Implementing (1) would cause an infinite loop of builds since the file thw
build would update is in the repo, and I don't think we want to play games
with not triggering builds when this or that file is changed.
For (2), the file location is standard, so it feels a bit redundant. The
Thank you very much for your help. I have updated to the latest version of
java 21 and it worked.
For me, the best place to put the Build Information would be in the Build
Section of the github pages since I would not expect that information to be
in a readme or POM file anymore. It has become
On Tue, 12 Dec 2023 at 14:21, Alex Herbert wrote:
>
> On Tue, 12 Dec 2023 at 13:20, Gary Gregory wrote:
> >
> > What's the best way to document this do you think?
>
> That lang is tested (and so should be built) with the latest JDK of
> the respective stable release (8, 11, 17, 21)?
>
> This
On Tue, 12 Dec 2023 at 13:20, Gary Gregory wrote:
>
> What's the best way to document this do you think?
That lang is tested (and so should be built) with the latest JDK of
the respective stable release (8, 11, 17, 21)?
This could live on the README in the GH repo. This would require an
update
What's the best way to document this do you think?
Gary
On Tue, Dec 12, 2023, 7:19 AM Alex Herbert wrote:
> I updated JDK 17.0.6 to 17.0.9 and lang now builds on my mac:
>
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Java version: 17.0.9, vendor: Eclipse Adoptium, runtime:
I updated JDK 17.0.6 to 17.0.9 and lang now builds on my mac:
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Java version: 17.0.9, vendor: Eclipse Adoptium, runtime:
/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
Default locale: en_GB, platform encoding: UTF-8
OS
See the GutHub builds as well. Make sure you have the latest Java version
of the major release line you are using, which is not the case here, and
might not matter.
Note that some of the tests make allowances for bugs in the JDK date
classes.
Gary
On Tue, Dec 12, 2023, 6:18 AM Alex Herbert
I can confirm I see 3 test failures in the FastDateParser using:
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Java version: 17.0.6, vendor: Eclipse Adoptium, runtime:
/Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home
Default locale: en_GB, platform encoding: UTF-8
OS
Hello and thanks for your help.
How do I compile or did I find a bug ?
I have been been attempting to build the latest version of Apache
Common-Lang.
The GitHub repository that I have used is
https://github.com/apache/commons-lang.git
I have the billed instructions mentioned in the following
12 matches
Mail list logo
