[
https://issues.apache.org/jira/browse/XALANJ-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Kesselman updated XALANJ-2707:
----------------------------------
Description:
*Possible blocker for XALANJ-2651*
In decompiling the xalan2j-taglet code as part of the maven build effort, we
discovered that it appears to have dependencies upon com.sun.* code which Went
Away after Java 8. We'd been getting away with it because we'd been running
from a prebuilt jarfile, but as it stands this may interfere with doing a full
build on more recent Java releases.
Current thoughts:
0) Build only on Java 8. Ugh.
1) Build javadocs only on Java 8, accept that they fail elsewhere. Less ugh,
but still ugh.
2) Check in a canned copy of this module's jarfile, so we can run without
building it. That's essentially what we were doing in pre-Mavenization days.
Perhaps not rebuild it automagically as part of Xalan build.
3) Post this taglet module to Maven, reference it from there, so Xalan build
doesn't have to deal with the issue.
4) Make the taglet code introspect and use the newer or older interfaces to
those functions as available.
Right now I'm treating this as technical debt, but we should consider whether
switching to Maven requires resolving it.
was:
In decompiling the xalan2j-taglet code as part of the maven build effort, we
discovered that it appears to have dependencies upon com.sun.* code which Went
Away after Java 8. We'd been getting away with it because we'd been running
from a prebuilt jarfile, but as it stands this may interfere with doing a full
build on more recent Java releases.
Current thoughts:
0) Build only on Java 8. Ugh.
1) Build javadocs only on Java 8, accept that they fail elsewhere. Less ugh,
but still ugh.
2) Check in a canned copy of this module's jarfile, so we can run without
building it. That's essentially what we were doing in pre-Mavenization days.
Perhaps not rebuild it automagically as part of Xalan build.
3) Post this taglet module to Maven, reference it from there, so Xalan build
doesn't have to deal with the issue.
4) Make the taglet code introspect and use the newer or older interfaces to
those functions as available.
Right now I'm treating this as technical debt, but we should consider whether
switching to Maven requires resolving it.
> Javadoc taglet depends upon deprecated classes?
> -----------------------------------------------
>
> Key: XALANJ-2707
> URL: https://issues.apache.org/jira/browse/XALANJ-2707
> Project: XalanJ2
> Issue Type: Improvement
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Documentation
> Environment: JDK more recent than 1.8
> Reporter: Joe Kesselman
> Priority: Major
> Labels: build, documentation, java-migration
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> *Possible blocker for XALANJ-2651*
> In decompiling the xalan2j-taglet code as part of the maven build effort, we
> discovered that it appears to have dependencies upon com.sun.* code which
> Went Away after Java 8. We'd been getting away with it because we'd been
> running from a prebuilt jarfile, but as it stands this may interfere with
> doing a full build on more recent Java releases.
> Current thoughts:
> 0) Build only on Java 8. Ugh.
> 1) Build javadocs only on Java 8, accept that they fail elsewhere. Less ugh,
> but still ugh.
> 2) Check in a canned copy of this module's jarfile, so we can run without
> building it. That's essentially what we were doing in pre-Mavenization days.
> Perhaps not rebuild it automagically as part of Xalan build.
> 3) Post this taglet module to Maven, reference it from there, so Xalan build
> doesn't have to deal with the issue.
> 4) Make the taglet code introspect and use the newer or older interfaces to
> those functions as available.
> Right now I'm treating this as technical debt, but we should consider whether
> switching to Maven requires resolving it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
