Apologies Greg,

it appears 2011 tldgen does not yet accomodate javax.lang.model and 
com.sun.source API types for Java 11

I'll propose that suggestion but for now we may need hard conversion types for 
generated source
(assuming the class names are spot on..which they probably are not)

Thanks for the link
Martin-
________________________________
From: Greg Huber <gregh3...@gmail.com>
Sent: Thursday, April 14, 2022 3:13 AM
To: dev@struts.apache.org <dev@struts.apache.org>
Subject: Re: tld generator

Martin,

I had three ways of generating the tlds, this was one of them. They all
use the com.sun.javadoc API which has been rewritten, and now not
convertible.

from the migration guide:

https://docs.oracle.com/en/java/javase/11/docs/api/jdk.javadoc/jdk/javadoc/doclet/package-summary.html

Many of the types in the old com.sun.javadoc API do not have equivalents
in this package. Instead, types in the javax.lang.model and
com.sun.source APIs are used instead. The following table gives a guide
to the mapping from old types to their replacements. In some cases,
there is no direct equivalent.

On 13/04/2022 18:01, Martin Gainty wrote:
> Hi Greg
>
> Have you tried tldgen?
> Google Code Archive - Long-term storage for Google Code Project 
> Hosting.<https://code.google.com/archive/p/tld-generator/>
> ________________________________
> From: Greg Huber <gregh3...@gmail.com>
> Sent: Wednesday, April 13, 2022 5:57 AM
> To: Struts Developers List <dev@struts.apache.org>
> Subject: tld generator
>
> I need a new tld generator for my jsp files.  The jdk.javadoc thing
> seems to have broken my builds.
>
> Can anyone recommend one going forward?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Reply via email to