On Thu, Jan 12, 2023 at 3:03 PM Mark Thomas wrote:
>
> On 12/01/2023 13:41, Rémy Maucherat wrote:
> > On Thu, Jan 12, 2023 at 1:19 PM Mark Thomas wrote:
> >>
> >> I tried switching the CI over to use Java 17 last night. This exposed an
> >> unexpected Javadoc behaviour that is currently breaking
Mark,
On 1/12/23 07:19, Mark Thomas wrote:
I tried switching the CI over to use Java 17 last night. This exposed an
unexpected Javadoc behaviour that is currently breaking the 9.0.x and
8.5.x builds.
Ant is configured to run Javadoc with failonwarning="true"
When running the Javadoc task
On 12/01/2023 13:41, Rémy Maucherat wrote:
On Thu, Jan 12, 2023 at 1:19 PM Mark Thomas wrote:
I tried switching the CI over to use Java 17 last night. This exposed an
unexpected Javadoc behaviour that is currently breaking the 9.0.x and
8.5.x builds.
Ant is configured to run Javadoc with
On Thu, Jan 12, 2023 at 1:19 PM Mark Thomas wrote:
>
> I tried switching the CI over to use Java 17 last night. This exposed an
> unexpected Javadoc behaviour that is currently breaking the 9.0.x and
> 8.5.x builds.
>
> Ant is configured to run Javadoc with failonwarning="true"
>
> When running
I tried switching the CI over to use Java 17 last night. This exposed an
unexpected Javadoc behaviour that is currently breaking the 9.0.x and
8.5.x builds.
Ant is configured to run Javadoc with failonwarning="true"
When running the Javadoc task with Java 17:
- if source="11" (Tomcat 10.1.x
