You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@freemarker.apache.org by "Daniel Dekany (JIRA)" <ji...@apache.org> on 2018/09/26 21:51:00 UTC
[jira] [Comment Edited] (FREEMARKER-104) Java 11 Compatibility
Problem
[ https://issues.apache.org/jira/browse/FREEMARKER-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629452#comment-16629452 ]
Daniel Dekany edited comment on FREEMARKER-104 at 9/26/18 9:50 PM:
-------------------------------------------------------------------
I have checked if we can use {{javax.xml.xpath}}, but its API is too restricted for our purposes. So it seems we can still only support XPath if Xalan (even under com.sun, when we are allowed to access it) or Jaxen is present.
was (Author: ddekany):
I have checked if we can use {{javax.xml.xpath}}, but its API is too restricted for out purposes. So it seems we can still only support XPath if Xalan (even under com.sun, when we are allowed to access it) or Jaxen is present.
> Java 11 Compatibility Problem
> -----------------------------
>
> Key: FREEMARKER-104
> URL: https://issues.apache.org/jira/browse/FREEMARKER-104
> Project: Apache Freemarker
> Issue Type: Improvement
> Affects Versions: 2.3.28
> Reporter: Krzysztof Dragan
> Priority: Critical
>
> Hi all,
> I am developer from PTC company. We are working on update our system to Java 11.
> Compiling system with newest jdk we noticed problems with using of java internal xml api.
> Are you planning new release of freemarker.jar with java 11 support?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)