Re: Apache Common Lang -- How do I compile or did I find a bug
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 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 Gregory > > wrote: > > > > > 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 > > > Java requirement is in pom.xml. The Maven requirement is unspecified > > unless > > > the Maven enforcer plug in is configured. > > > > > > There is no hard process for assigning issues. I don't think non-Apache > > > folk can assign issues. You can ask to be assigned but it's not > sometimes > > > usually worth hassling with. > > > > > > Gary > > > > > > On Tue, Dec 12, 2023, 1:51 PM Charles Stockman < > > charlesstockm...@gmail.com > > > > > > > wrote: > > > > > > > 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 a pseudo standard > that > > I > > > > would look on Github for instructions on building. > > > > > > > > Suggestions > > > > > > > >1. Is there some that we can dynamically update the GitHub Page so > > > that > > > >we can include the version of Java and Maven that the CI has used > > > >2. In the Github repo under the Build Instructions can we add a > link > > > to > > > >the file that the contains the build information and can it have > the > > > > title > > > >approximating the text "Maven and Java Version needed" > > > > > > > > I have selected a Jira Issue that I would enjoy working on. The > steps > > > > should be to create a Jira Account and then do I assign myself to the > > > issue > > > > or is there some process. > > > > > > > > Thanks for your help > > > > Charles Stockman. > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Dec 12, 2023 at 11:00 AM sebb wrote: > > > > > > > > > On Tue, 12 Dec 2023 at 14:21, Alex Herbert < > alex.d.herb...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > On Tue, 12 Dec 2023 at 13:20, Gary Gregory < > garydgreg...@gmail.com > > > > > > > > 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 to the commons-build-plugin that generates it. > > > > > > > > > > The build plugin includes the POM description text, so it can be > > added > > > > > there. > > > > > > > > > > > But for a start > > > > > > we can add a few sentences to the lang README under the building > > > > > > section: > > > > > > > > > > > > "The code is tested using the latest revision of the JDK for > > > supported > > > > > > LTS releases. Please ensure your build environment is up-to-date > > and > > > > > > kindly report any build issues." > > > > > > > > > > > > This should provide a first indicator to a user that the JDK must > > be > > > > > > up-to-date and welcomes any feedback on building. This text may > not > > > be > > > > > > suitable for all repos if they do not test across all LTS > versions > > of > > > > > > the JDK so may need some revision for the build-plugin. > > > > > > > > > > > > Alex > > > > > > > > > > > > > > - > > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > > > >
Re: Apache Common Lang -- How do I compile or did I find a bug
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 Gregory > wrote: > > > 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 > > Java requirement is in pom.xml. The Maven requirement is unspecified > unless > > the Maven enforcer plug in is configured. > > > > There is no hard process for assigning issues. I don't think non-Apache > > folk can assign issues. You can ask to be assigned but it's not sometimes > > usually worth hassling with. > > > > Gary > > > > On Tue, Dec 12, 2023, 1:51 PM Charles Stockman < > charlesstockm...@gmail.com > > > > > wrote: > > > > > 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 a pseudo standard that > I > > > would look on Github for instructions on building. > > > > > > Suggestions > > > > > >1. Is there some that we can dynamically update the GitHub Page so > > that > > >we can include the version of Java and Maven that the CI has used > > >2. In the Github repo under the Build Instructions can we add a link > > to > > >the file that the contains the build information and can it have the > > > title > > >approximating the text "Maven and Java Version needed" > > > > > > I have selected a Jira Issue that I would enjoy working on. The steps > > > should be to create a Jira Account and then do I assign myself to the > > issue > > > or is there some process. > > > > > > Thanks for your help > > > Charles Stockman. > > > > > > > > > > > > > > > > > > On Tue, Dec 12, 2023 at 11:00 AM sebb wrote: > > > > > > > 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 could live on the README in the GH repo. This would require an > > > > > update to the commons-build-plugin that generates it. > > > > > > > > The build plugin includes the POM description text, so it can be > added > > > > there. > > > > > > > > > But for a start > > > > > we can add a few sentences to the lang README under the building > > > > > section: > > > > > > > > > > "The code is tested using the latest revision of the JDK for > > supported > > > > > LTS releases. Please ensure your build environment is up-to-date > and > > > > > kindly report any build issues." > > > > > > > > > > This should provide a first indicator to a user that the JDK must > be > > > > > up-to-date and welcomes any feedback on building. This text may not > > be > > > > > suitable for all repos if they do not test across all LTS versions > of > > > > > the JDK so may need some revision for the build-plugin. > > > > > > > > > > Alex > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > >
Re: Apache Common Lang -- How do I compile or did I find a bug
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 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 > Java requirement is in pom.xml. The Maven requirement is unspecified unless > the Maven enforcer plug in is configured. > > There is no hard process for assigning issues. I don't think non-Apache > folk can assign issues. You can ask to be assigned but it's not sometimes > usually worth hassling with. > > Gary > > On Tue, Dec 12, 2023, 1:51 PM Charles Stockman > > wrote: > > > 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 a pseudo standard that I > > would look on Github for instructions on building. > > > > Suggestions > > > >1. Is there some that we can dynamically update the GitHub Page so > that > >we can include the version of Java and Maven that the CI has used > >2. In the Github repo under the Build Instructions can we add a link > to > >the file that the contains the build information and can it have the > > title > >approximating the text "Maven and Java Version needed" > > > > I have selected a Jira Issue that I would enjoy working on. The steps > > should be to create a Jira Account and then do I assign myself to the > issue > > or is there some process. > > > > Thanks for your help > > Charles Stockman. > > > > > > > > > > > > On Tue, Dec 12, 2023 at 11:00 AM sebb wrote: > > > > > 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 could live on the README in the GH repo. This would require an > > > > update to the commons-build-plugin that generates it. > > > > > > The build plugin includes the POM description text, so it can be added > > > there. > > > > > > > But for a start > > > > we can add a few sentences to the lang README under the building > > > > section: > > > > > > > > "The code is tested using the latest revision of the JDK for > supported > > > > LTS releases. Please ensure your build environment is up-to-date and > > > > kindly report any build issues." > > > > > > > > This should provide a first indicator to a user that the JDK must be > > > > up-to-date and welcomes any feedback on building. This text may not > be > > > > suitable for all repos if they do not test across all LTS versions of > > > > the JDK so may need some revision for the build-plugin. > > > > > > > > Alex > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > >
Re: Apache Common Lang -- How do I compile or did I find a bug
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 Java requirement is in pom.xml. The Maven requirement is unspecified unless the Maven enforcer plug in is configured. There is no hard process for assigning issues. I don't think non-Apache folk can assign issues. You can ask to be assigned but it's not sometimes usually worth hassling with. Gary On Tue, Dec 12, 2023, 1:51 PM Charles Stockman wrote: > 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 a pseudo standard that I > would look on Github for instructions on building. > > Suggestions > >1. Is there some that we can dynamically update the GitHub Page so that >we can include the version of Java and Maven that the CI has used >2. In the Github repo under the Build Instructions can we add a link to >the file that the contains the build information and can it have the > title >approximating the text "Maven and Java Version needed" > > I have selected a Jira Issue that I would enjoy working on. The steps > should be to create a Jira Account and then do I assign myself to the issue > or is there some process. > > Thanks for your help > Charles Stockman. > > > > > > On Tue, Dec 12, 2023 at 11:00 AM sebb wrote: > > > 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 could live on the README in the GH repo. This would require an > > > update to the commons-build-plugin that generates it. > > > > The build plugin includes the POM description text, so it can be added > > there. > > > > > But for a start > > > we can add a few sentences to the lang README under the building > > > section: > > > > > > "The code is tested using the latest revision of the JDK for supported > > > LTS releases. Please ensure your build environment is up-to-date and > > > kindly report any build issues." > > > > > > This should provide a first indicator to a user that the JDK must be > > > up-to-date and welcomes any feedback on building. This text may not be > > > suitable for all repos if they do not test across all LTS versions of > > > the JDK so may need some revision for the build-plugin. > > > > > > Alex > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > >
Re: Apache Common Lang -- How do I compile or did I find a bug
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 a pseudo standard that I would look on Github for instructions on building. Suggestions 1. Is there some that we can dynamically update the GitHub Page so that we can include the version of Java and Maven that the CI has used 2. In the Github repo under the Build Instructions can we add a link to the file that the contains the build information and can it have the title approximating the text "Maven and Java Version needed" I have selected a Jira Issue that I would enjoy working on. The steps should be to create a Jira Account and then do I assign myself to the issue or is there some process. Thanks for your help Charles Stockman. On Tue, Dec 12, 2023 at 11:00 AM sebb wrote: > 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 could live on the README in the GH repo. This would require an > > update to the commons-build-plugin that generates it. > > The build plugin includes the POM description text, so it can be added > there. > > > But for a start > > we can add a few sentences to the lang README under the building > > section: > > > > "The code is tested using the latest revision of the JDK for supported > > LTS releases. Please ensure your build environment is up-to-date and > > kindly report any build issues." > > > > This should provide a first indicator to a user that the JDK must be > > up-to-date and welcomes any feedback on building. This text may not be > > suitable for all repos if they do not test across all LTS versions of > > the JDK so may need some revision for the build-plugin. > > > > Alex > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: Apache Common Lang -- How do I compile or did I find a bug
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 could live on the README in the GH repo. This would require an > update to the commons-build-plugin that generates it. The build plugin includes the POM description text, so it can be added there. > But for a start > we can add a few sentences to the lang README under the building > section: > > "The code is tested using the latest revision of the JDK for supported > LTS releases. Please ensure your build environment is up-to-date and > kindly report any build issues." > > This should provide a first indicator to a user that the JDK must be > up-to-date and welcomes any feedback on building. This text may not be > suitable for all repos if they do not test across all LTS versions of > the JDK so may need some revision for the build-plugin. > > Alex > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Apache Common Lang -- How do I compile or did I find a bug
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 to the commons-build-plugin that generates it. But for a start we can add a few sentences to the lang README under the building section: "The code is tested using the latest revision of the JDK for supported LTS releases. Please ensure your build environment is up-to-date and kindly report any build issues." This should provide a first indicator to a user that the JDK must be up-to-date and welcomes any feedback on building. This text may not be suitable for all repos if they do not test across all LTS versions of the JDK so may need some revision for the build-plugin. Alex - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: Apache Common Lang -- How do I compile or did I find a bug
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: > /Library/Java/JavaVirtualMachines/temurin-17.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" > > So this is a JDK issue. > > Alex > > On Tue, 12 Dec 2023 at 11:51, Gary Gregory wrote: > > > > 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 > wrote: > > > > > 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 name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" > > > > > > --- > > > [ERROR] > > > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_DateFormatSymbols:82->testTimeZoneStrategyPattern_DateFormatSymbols_getZoneStrings:147 > > > java.text.ParseException: Unparseable date: Tempo universale > > > coordinato: with locale = it, zIndex = 3, tzDisplay = 'Tempo > > > universale coordinato', parser = 'FastDateParser[z, it, GMT]' > > > [ERROR] > > > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_DateFormatSymbols:82->testTimeZoneStrategyPattern_DateFormatSymbols_getZoneStrings:147 > > > java.text.ParseException: Unparseable date: 세계 표준시: with locale = ko, > > > zIndex = 3, tzDisplay = '세계 표준시', parser = 'FastDateParser[z, ko, > > > GMT]' > > > [ERROR] > > > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_TimeZone:88->testTimeZoneStrategyPattern_TimeZone_getAvailableIDs:172 > > > java.text.ParseException: Unparseable date: normaltid – Kanton: with > > > locale = nb, id = 'Pacific/Kanton', timeZone = > > > > > > > sun.util.calendar.ZoneInfo[id="Pacific/Kanton",offset=4680,dstSavings=0,useDaylight=false,transitions=5,lastRule=null] > > > ... > > > --- > > > > > > Build is fine using on MacOS using: > > > > > > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) > > > Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: > > > /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home > > > Default locale: en_GB, platform encoding: UTF-8 > > > OS name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" > > > > > > Build is fine on Linux JDK 17 using: > > > > > > Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > > > Java version: 17.0.4.1, vendor: Oracle Corporation, runtime: > > > /usr/lib/jvm/jdk-17.0.4.1 > > > Default locale: en_GB, platform encoding: UTF-8 > > > OS name: "linux", version: "5.4.0-167-generic", arch: "amd64", family: > > > "unix" > > > > > > The GH actions builds are green for MacOS latest on all JDKs. I see > > > you are using a similar OS version to my mac. So this may be a MacOS > > > Sonoma 14 vs MacOS Ventura 13 issue. It would be good if someone else > > > can replicate it on MacOS. > > > > > > Alex > > > > > > On Tue, 12 Dec 2023 at 08:52, Charles Stockman > > > wrote: > > > > > > > > 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 section : > > > > > > > > https://github.com/apache/commons-lang?tab=3Dreadme-ov-file#building > > > > > > > > > > > > The maven and java version that I have used is: > > > > > > > > > > > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > > > > > > > > Maven home: /opt/homebrew/Cellar/maven/3.9.6/libexec > > > > > > > > Java version: 17.0.7, vendor: Eclipse Adoptium, runtime: = > > > > > > > > /Users/charlesstockman/.sdkman/candidates/java/17.0.7-tem > > > > > > > > Default locale: en_US, platform encoding: UTF-8 > > > > > > > > OS name: "mac os x", version: "13.4", arch: "aarch64", family: = > > > > > > > > "mac" > > > > > > > > > > > > The steps were > > > > > > > > > > > > 1. git clone https://github.com/apache/commons-lang.git > > > > > > > > 1. cd commons-lang > > > > > > > > 2. mvn > > > > > > > > > > > > I have received the following error and attached the output > > > > > > > > > > > > > > > > [ERROR] Failed to execute goal > > >
Re: Apache Common Lang -- How do I compile or did I find a bug
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 name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" So this is a JDK issue. Alex On Tue, 12 Dec 2023 at 11:51, Gary Gregory wrote: > > 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 wrote: > > > 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 name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" > > > > --- > > [ERROR] > > > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_DateFormatSymbols:82->testTimeZoneStrategyPattern_DateFormatSymbols_getZoneStrings:147 > > java.text.ParseException: Unparseable date: Tempo universale > > coordinato: with locale = it, zIndex = 3, tzDisplay = 'Tempo > > universale coordinato', parser = 'FastDateParser[z, it, GMT]' > > [ERROR] > > > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_DateFormatSymbols:82->testTimeZoneStrategyPattern_DateFormatSymbols_getZoneStrings:147 > > java.text.ParseException: Unparseable date: 세계 표준시: with locale = ko, > > zIndex = 3, tzDisplay = '세계 표준시', parser = 'FastDateParser[z, ko, > > GMT]' > > [ERROR] > > > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_TimeZone:88->testTimeZoneStrategyPattern_TimeZone_getAvailableIDs:172 > > java.text.ParseException: Unparseable date: normaltid – Kanton: with > > locale = nb, id = 'Pacific/Kanton', timeZone = > > > > sun.util.calendar.ZoneInfo[id="Pacific/Kanton",offset=4680,dstSavings=0,useDaylight=false,transitions=5,lastRule=null] > > ... > > --- > > > > Build is fine using on MacOS using: > > > > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) > > Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: > > /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home > > Default locale: en_GB, platform encoding: UTF-8 > > OS name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" > > > > Build is fine on Linux JDK 17 using: > > > > Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > > Java version: 17.0.4.1, vendor: Oracle Corporation, runtime: > > /usr/lib/jvm/jdk-17.0.4.1 > > Default locale: en_GB, platform encoding: UTF-8 > > OS name: "linux", version: "5.4.0-167-generic", arch: "amd64", family: > > "unix" > > > > The GH actions builds are green for MacOS latest on all JDKs. I see > > you are using a similar OS version to my mac. So this may be a MacOS > > Sonoma 14 vs MacOS Ventura 13 issue. It would be good if someone else > > can replicate it on MacOS. > > > > Alex > > > > On Tue, 12 Dec 2023 at 08:52, Charles Stockman > > wrote: > > > > > > 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 section : > > > > > > https://github.com/apache/commons-lang?tab=3Dreadme-ov-file#building > > > > > > > > > The maven and java version that I have used is: > > > > > > > > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > > > > > > Maven home: /opt/homebrew/Cellar/maven/3.9.6/libexec > > > > > > Java version: 17.0.7, vendor: Eclipse Adoptium, runtime: = > > > > > > /Users/charlesstockman/.sdkman/candidates/java/17.0.7-tem > > > > > > Default locale: en_US, platform encoding: UTF-8 > > > > > > OS name: "mac os x", version: "13.4", arch: "aarch64", family: = > > > > > > "mac" > > > > > > > > > The steps were > > > > > > > > > 1. git clone https://github.com/apache/commons-lang.git > > > > > > 1. cd commons-lang > > > > > > 2. mvn > > > > > > > > > I have received the following error and attached the output > > > > > > > > > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-surefire-plugin:3.2.2:test (default-test) on > > project commons-lang3: There are test failures. > > > > > > [ERROR] > > > > > > [ERROR] Please refer to > > /Users/charlesstockman/otherGit/commons-lang/target/surefire-reports for > > the individual test results. > > > > > > [ERROR] Please refer to dump files (if any exist) [date].dump, > >
Re: Apache Common Lang -- How do I compile or did I find a bug
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 wrote: > 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 name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" > > --- > [ERROR] > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_DateFormatSymbols:82->testTimeZoneStrategyPattern_DateFormatSymbols_getZoneStrings:147 > java.text.ParseException: Unparseable date: Tempo universale > coordinato: with locale = it, zIndex = 3, tzDisplay = 'Tempo > universale coordinato', parser = 'FastDateParser[z, it, GMT]' > [ERROR] > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_DateFormatSymbols:82->testTimeZoneStrategyPattern_DateFormatSymbols_getZoneStrings:147 > java.text.ParseException: Unparseable date: 세계 표준시: with locale = ko, > zIndex = 3, tzDisplay = '세계 표준시', parser = 'FastDateParser[z, ko, > GMT]' > [ERROR] > > FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_TimeZone:88->testTimeZoneStrategyPattern_TimeZone_getAvailableIDs:172 > java.text.ParseException: Unparseable date: normaltid – Kanton: with > locale = nb, id = 'Pacific/Kanton', timeZone = > > sun.util.calendar.ZoneInfo[id="Pacific/Kanton",offset=4680,dstSavings=0,useDaylight=false,transitions=5,lastRule=null] > ... > --- > > Build is fine using on MacOS using: > > Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) > Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: > /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" > > Build is fine on Linux JDK 17 using: > > Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) > Java version: 17.0.4.1, vendor: Oracle Corporation, runtime: > /usr/lib/jvm/jdk-17.0.4.1 > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-167-generic", arch: "amd64", family: > "unix" > > The GH actions builds are green for MacOS latest on all JDKs. I see > you are using a similar OS version to my mac. So this may be a MacOS > Sonoma 14 vs MacOS Ventura 13 issue. It would be good if someone else > can replicate it on MacOS. > > Alex > > On Tue, 12 Dec 2023 at 08:52, Charles Stockman > wrote: > > > > 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 section : > > > > https://github.com/apache/commons-lang?tab=3Dreadme-ov-file#building > > > > > > The maven and java version that I have used is: > > > > > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > > > > Maven home: /opt/homebrew/Cellar/maven/3.9.6/libexec > > > > Java version: 17.0.7, vendor: Eclipse Adoptium, runtime: = > > > > /Users/charlesstockman/.sdkman/candidates/java/17.0.7-tem > > > > Default locale: en_US, platform encoding: UTF-8 > > > > OS name: "mac os x", version: "13.4", arch: "aarch64", family: = > > > > "mac" > > > > > > The steps were > > > > > > 1. git clone https://github.com/apache/commons-lang.git > > > > 1. cd commons-lang > > > > 2. mvn > > > > > > I have received the following error and attached the output > > > > > > > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:3.2.2:test (default-test) on > project commons-lang3: There are test failures. > > > > [ERROR] > > > > [ERROR] Please refer to > /Users/charlesstockman/otherGit/commons-lang/target/surefire-reports for > the individual test results. > > > > [ERROR] Please refer to dump files (if any exist) [date].dump, > [date]-jvmRun[N].dump and [date].dumpstream. > > > > [ERROR] -> [Help 1] > > > > [ERROR] > > > > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e switch. > > > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > > > [ERROR] > > > > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > > > > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > > > > charlesstockman@Charless-Mini commons-lang % > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional
Re: Apache Common Lang -- How do I compile or did I find a bug
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 name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" --- [ERROR] FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_DateFormatSymbols:82->testTimeZoneStrategyPattern_DateFormatSymbols_getZoneStrings:147 java.text.ParseException: Unparseable date: Tempo universale coordinato: with locale = it, zIndex = 3, tzDisplay = 'Tempo universale coordinato', parser = 'FastDateParser[z, it, GMT]' [ERROR] FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_DateFormatSymbols:82->testTimeZoneStrategyPattern_DateFormatSymbols_getZoneStrings:147 java.text.ParseException: Unparseable date: 세계 표준시: with locale = ko, zIndex = 3, tzDisplay = '세계 표준시', parser = 'FastDateParser[z, ko, GMT]' [ERROR] FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategy_TimeZone:88->testTimeZoneStrategyPattern_TimeZone_getAvailableIDs:172 java.text.ParseException: Unparseable date: normaltid – Kanton: with locale = nb, id = 'Pacific/Kanton', timeZone = sun.util.calendar.ZoneInfo[id="Pacific/Kanton",offset=4680,dstSavings=0,useDaylight=false,transitions=5,lastRule=null] ... --- Build is fine using on MacOS using: Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) Java version: 11.0.18, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home Default locale: en_GB, platform encoding: UTF-8 OS name: "mac os x", version: "13.4.1", arch: "aarch64", family: "mac" Build is fine on Linux JDK 17 using: Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) Java version: 17.0.4.1, vendor: Oracle Corporation, runtime: /usr/lib/jvm/jdk-17.0.4.1 Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "5.4.0-167-generic", arch: "amd64", family: "unix" The GH actions builds are green for MacOS latest on all JDKs. I see you are using a similar OS version to my mac. So this may be a MacOS Sonoma 14 vs MacOS Ventura 13 issue. It would be good if someone else can replicate it on MacOS. Alex On Tue, 12 Dec 2023 at 08:52, Charles Stockman wrote: > > 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 section : > > https://github.com/apache/commons-lang?tab=3Dreadme-ov-file#building > > > The maven and java version that I have used is: > > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > > Maven home: /opt/homebrew/Cellar/maven/3.9.6/libexec > > Java version: 17.0.7, vendor: Eclipse Adoptium, runtime: = > > /Users/charlesstockman/.sdkman/candidates/java/17.0.7-tem > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "13.4", arch: "aarch64", family: = > > "mac" > > > The steps were > > > 1. git clone https://github.com/apache/commons-lang.git > > 1. cd commons-lang > > 2. mvn > > > I have received the following error and attached the output > > > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:3.2.2:test (default-test) on > project commons-lang3: There are test failures. > > [ERROR] > > [ERROR] Please refer to > /Users/charlesstockman/otherGit/commons-lang/target/surefire-reports for the > individual test results. > > [ERROR] Please refer to dump files (if any exist) [date].dump, > [date]-jvmRun[N].dump and [date].dumpstream. > > [ERROR] -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > > charlesstockman@Charless-Mini commons-lang % > > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Apache Common Lang -- How do I compile or did I find a bug
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 section : https://github.com/apache/commons-lang?tab=3Dreadme-ov-file#building The maven and java version that I have used is: Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) Maven home: /opt/homebrew/Cellar/maven/3.9.6/libexec Java version: 17.0.7, vendor: Eclipse Adoptium, runtime: = /Users/charlesstockman/.sdkman/candidates/java/17.0.7-tem Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "13.4", arch: "aarch64", family: = "mac" The steps were 1. git clone https://github.com/apache/commons-lang.git 1. cd commons-lang 2. mvn I have received the following error and attached the output [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.2.2:test (default-test) on project commons-lang3: There are test failures. [ERROR] [ERROR] Please refer to /Users/charlesstockman/otherGit/commons-lang/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException charlesstockman@Charless-Mini commons-lang % <>
