Re: next derby release
May be 10.15.2 realeased with Java 9 10.15.3-SNAPSHOT in development with Java 11 (or whatever is the next development name) ? Bye, Davide On 05/01/2020 18:48, Rick Hillegas wrote: It's been a year since we produced a Derby release. No significant feature work has gone into the code since then. But I would be happy to manage a 10.15.2 maintenance release in order to roll up the handful of bug fixes which have accumulated over the last year. The only reason I can see for a new feature release would be to advance the minimal JVM version to the Java 11 LTS version. According to convention, this would require a vote by the community. I am not planning any work over the next year which would require Java 11 features, so I don't personally see any compelling reason for advancing the JVM version. What are your thoughts? Thanks, -Rick -- Ing. Davide Grandi email : davide.gra...@email.it mobile : +39 339 7468 778
next derby release
It's been a year since we produced a Derby release. No significant feature work has gone into the code since then. But I would be happy to manage a 10.15.2 maintenance release in order to roll up the handful of bug fixes which have accumulated over the last year. The only reason I can see for a new feature release would be to advance the minimal JVM version to the Java 11 LTS version. According to convention, this would require a vote by the community. I am not planning any work over the next year which would require Java 11 features, so I don't personally see any compelling reason for advancing the JVM version. What are your thoughts? Thanks, -Rick
[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0
[ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008364#comment-17008364 ] Richard N. Hillegas commented on DERBY-7063: Thanks for raising the topic of a Derby release. I will move this discussion over to the dev list. > Cannot connect using squirrel 3.3.0 > --- > > Key: DERBY-7063 > URL: https://issues.apache.org/jira/browse/DERBY-7063 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Server >Affects Versions: 10.15.1.3 >Reporter: sagar >Priority: Major > Fix For: 10.15.1.3 > > > The derbyclient.jar file does not have the > org.apache.derby.jdbc.ClientDriver.class > > When I add the jar file in squirrel, ssquirrel automatically detects the > driver but since this class is missing it does not detect it. > Till now I was using 10.11.1.1 database. Now I have decided to upgrade and > this issue cropped up. > > Yes Derby has switched to the module system from 10.15.1.3 but the derby > documentation mentions connection to Network Server similar to previous as > using the > org.apache.derby.jdbc.ClientDriver and this class is missing from the new > derbyclient.jar. > > > Squirrel is running on Java 1.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-6809) Java 1.8 feature use
[ https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008363#comment-17008363 ] Richard N. Hillegas commented on DERBY-6809: Thanks for volunteering to investigate these kinds of optimizations. It is likely that Derby performance would benefit from being run on more modern JVMs. Note that the current release policy is to compile Derby into Java 9 byte code. One practical consequence of this is that a submission can be committed only if it compiles cleanly on Java 9 and the tests pass on that JVM. We could, of course, hold a vote to move the byte code level forward to Java 11. That would make some sense since Java 11 is an LTS version and 9 isn't. > Java 1.8 feature use > > > Key: DERBY-6809 > URL: https://issues.apache.org/jira/browse/DERBY-6809 > Project: Derby > Issue Type: Improvement > Components: Network Server >Affects Versions: 11.0.0.0 >Reporter: sagar >Priority: Major > Attachments: 2017-12-04-143613_1366x768_scrot.png, binary_format.png, > latest.png, nb8.png > > > Suggestion ... > Is it possible to auto modify the existing source code using tools like > Netbeans, and take advantage of the new features in JDK 1.8 for better > multiuser performance and better utilization of current day multicore > processors? > Plainly put, can we have from 11.0 onwards a version of derby which takes > advantage of the advancements and new features in java 1.8 ... -- This message was sent by Atlassian Jira (v8.3.4#803005)
