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 <seb...@gmail.com> 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
>
>

Reply via email to