[ 
https://issues.apache.org/jira/browse/XALANJ-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787442#comment-17787442
 ] 

Alexander Kriegisch edited comment on XALANJ-2709 at 11/18/23 2:17 AM:
-----------------------------------------------------------------------

[~vladimirsitnikov], that was already discussed between Joe and me before I 
even started working on this PR. See my response to [your identical suggestion 
in the GitHub 
review|https://github.com/apache/xalan-java/pull/124#discussion_r1398030295]. 
There, you also find a quote of what Joe and I had discussed.


was (Author: kriegaex):
[~vladimirsitnikov], that was already discussed between Joe and me before I 
even started working on this PR. See my response to [your identical suggestion 
in the GitHub 
review|https://github.com/apache/xalan-java/pull/124#discussion_r1398030295]. 
There, you also find a quote of what Joe and I had discussed before.

> Enable project to be built on JDK 9+
> ------------------------------------
>
>                 Key: XALANJ-2709
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2709
>             Project: XalanJ2
>          Issue Type: New Feature
>      Security Level: No security risk; visible to anyone(Ordinary problems in 
> Xalan projects.  Anybody can view the issue.) 
>            Reporter: Alexander Kriegisch
>            Assignee: Gary D. Gregory
>            Priority: Major
>
> The current Maven build in branch {{xalan-java-mvn-refactored}} only works on 
> JDK 8, mostly due to the taglet module which uses {{sun.com.*}} APIs which 
> first were deprecated in JDK 9 and then later removed from the JDK entirely. 
> I.e., currently there is no option to build on JDK 9+ with source and target 
> 1.8.
> To do:
> * Duplicate taglet classes and modify the new version to use the current 
> taglet API in more recent JDKs, while still retaining the old JDK 8 classes. 
> Otherwise, it would no longer be possible to build Xalan-J on JDK 8.
> * Provide Maven profiles which auto-activate according to the currently used 
> JDK on the build system, which alternatively build the old or the new taglet 
> classes and use them later during javadoc generation.
> This way, it should still be possible to build the actual Xalan-J classes 
> with target 8. Only the taglet classes would be JDK-dependent.



--
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

Reply via email to