[
https://issues.apache.org/jira/browse/JXPATH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028926#comment-15028926
]
Michele Vivoda commented on JXPATH-184:
---------------------------------------
bq. I would rather finalize 1.4, publish and the focus on 2.0.
I agree
About 1.7, other examples: Spring Framework:
bq. JDK 6+ for Spring Framework 4.x JDK 5+ for Spring Framework 3.x
Hibernate 4.x
bq. Java 6 or higher (building Hibernate from source requires JDK 7 due to a
bug in the JDK 6 compiler).
In my opinion the issue is about the JDK a potential client library must
support. If a developer makes a library with tools for Spring 4.x he must
target jdk6 and it wont' be able to use JXPath as it nees jdk7. I am in this
situation, but I think many others are.
I would say start a new JXPath 2 with jdk6 and then see what happens, wait to
see if there is a real need of jdk7 and introduce it for an actual need.
> Update to Java 7
> ----------------
>
> Key: JXPATH-184
> URL: https://issues.apache.org/jira/browse/JXPATH-184
> Project: Commons JXPath
> Issue Type: Task
> Reporter: Benedikt Ritter
> Assignee: Benedikt Ritter
> Fix For: 1.4
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
