+1 BTW, I haven't heard you talk much about the jlink process. Sounds neat!
bryan On Thu, Feb 28, 2019 at 5:43 PM Rick Hillegas <rick.hille...@gmail.com> wrote: > > Thanks for the continued feedback, Bryan. I have added a sentence at the > end to address the supported JVM levels. > > I think it's ok to mention Java 9 even though it was short-lived and now > hard to come by. > > Here's rev 3: > > ---------------------------------- > > > The Apache Derby project is pleased to announce feature release 10.15.1.3. > > Apache Derby is a sub-project of the Apache DB project. Derby is a pure > Java relational database engine which conforms to the ISO/ANSI SQL and > JDBC standards. Derby aims to be easy for developers and end-users to > work with. > > Derby 10.15.1.3 can be obtained from the Derby download site: > > http://db.apache.org/derby/derby_downloads.html. > > 10.15.1.3 re-packages Derby as a set of JPMS modules. This introduces a > new jar file, derbyshared.jar, required by all configurations. Existing > users can continue to boot Derby with a classpath as they have always > done. Applications will run as they did on older Derby versions. > > Alternatively, users can now boot Derby with a module path. Doing so > provides extra security by encapsulating (hiding) Derby's internal > classes inside the new modules. > > Via the JDK's jlink tool, the new Derby modules can be assembled into > shrink-wrapped, footprint-optimized applications which deploy on > platforms lacking a JVM--platforms like smart phones and tablets. > > Users who want to study Derby's module structure may consult the module > diagrams in the 10.15 public API. > > Derby 10.15.1.3 runs on JVMs from Java 9 on up. > > Please try out this new release. > >
