[jira] [Commented] (JXPATH-184) Update to Java 7
[ https://issues.apache.org/jira/browse/JXPATH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15028841#comment-15028841 ] Sebb commented on JXPATH-184: - bq. Changed the group/artifact id to the new style of Apache Commons This can only be done if the package name is changed at the same time. Otherwise classpath issues can result > 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)
[jira] [Commented] (JXPATH-184) Update to Java 7
[ https://issues.apache.org/jira/browse/JXPATH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (JXPATH-184) Update to Java 7
[ https://issues.apache.org/jira/browse/JXPATH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15028971#comment-15028971 ] Michael Osipov commented on JXPATH-184: --- Thanks for pointing this out. Forgot it completely. > 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)
[jira] [Commented] (JXPATH-184) Update to Java 7
[ https://issues.apache.org/jira/browse/JXPATH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15027535#comment-15027535 ] Michael Osipov commented on JXPATH-184: --- 6 is end of life, 7 too. That should be enough, imho, to bump next major to 7. Commons IO website has been published on 17 February 2014, so Java 7 is fine. I assume IO3 will be Java 7. > 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)
[jira] [Commented] (JXPATH-184) Update to Java 7
[ https://issues.apache.org/jira/browse/JXPATH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15025211#comment-15025211 ] Benedikt Ritter commented on JXPATH-184: Agreed! > 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 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JXPATH-184) Update to Java 7
[ https://issues.apache.org/jira/browse/JXPATH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15026067#comment-15026067 ] Michele Vivoda commented on JXPATH-184: --- Hi, thanks for the work done in the last times, fantastic to see some action. About this issue: just for reference, up to now jxpath 1.4-SNAPSHOT was java 4 (and junit 3.8.1). I agree at some point it could upgrade, I am not sure about doing it in jxpath 1.4 that has many bug fixes and up to now is compatible with 1.3, that is the latest binary/Maven release. I would suggest to fix JXPATH-173 keeping JXPATH 1.4 as the last compatible with JDK1.4 and the previous versions of JXPath. Then start a JXPATH 1.5 with a newer JDK. To me 1.7 seems "too much", I checked for example Commons IO and is JDK1.6/5, not 7. Not sure about what would be actually needed from 1.7 > 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)
[jira] [Commented] (JXPATH-184) Update to Java 7
[ https://issues.apache.org/jira/browse/JXPATH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023162#comment-15023162 ] Michael Osipov commented on JXPATH-184: --- Very good issue, we should start with generics first.. > 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 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
