[BUILD-304] Migrate tldgen to Java 9 support Created: 15/May/18 Updated: 02/Nov/18 Resolved: 02/Nov/18 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Sang Ngo Huu | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Date of First Response: | |||||
| Account: | |||||
| Epic Link: | Build on JDK11+ | ||||
| Description |
|
We are using tldgen to generate document for JSP tag. It is does not work on Java9 and maintenanced We plan to migrate it to support Java 9. Refer the document for more detail |
| Comments |
| Comment by Dai Ha [ 15/May/18 ] |
|
Here is preference to java doc migration in case of upgrading this library by ourself: |
| Comment by Mikaël Geljić [ 15/May/18 ] |
|
Yup, here's the status here, as discussed yesterday in SoS or PDTM:
The shame is that we will continue performing releases on JDK8 for the foreseeable future anyway, so in practice we could keep it. My understanding from the last two scrums is that migrating is to Java 9 is not a trivial effort—although it would be a highly valuable training task. |
| Comment by Mikaël Geljić [ 22/May/18 ] |
|
And actually, looks like the output of tldgen was never used in the maven sites... see the 3 specific taglib reports; none of them is the one from tldgen (see screenshot). |
| Comment by Antti Hietala [ 02/Nov/18 ] |
|
Obsolete since we deprecate JSP support with DEV-1058 |