[
https://issues.apache.org/jira/browse/DERBY-6854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295213#comment-15295213
]
Bryan Pendleton commented on DERBY-6854:
----------------------------------------
Thanks for the references and discussion. I agree: this seems unlikely to
disrupt the
way we arrange for our driver(s) to be available for applications.
I reacted a little nervously, because I've learned over the years that one of
the
trickiest parts of using Derby for application developers who are just getting
started
is to manage the CLASSPATH to get the Derby classes in place appropriately.
It seems like it should be straightforward, but it's terribly challenging, as
witnessed
by literally dozens of StackOverflow queries over the years by developers who
either can't get their JDBC driver loaded at all, or somehow managed to get
multiple different copies of Derby into their CLASSPATH and can't figure out
why.
Hopefully Oracle will be careful with this new classloading behavior, and won't
make an already complicated situation worse.
But, w.r.t. your proposal to add the doPrivileged blocks, +1 from me, and
thanks !
> Make it possible to run Derby tests on early access versions of JDK 9
> ---------------------------------------------------------------------
>
> Key: DERBY-6854
> URL: https://issues.apache.org/jira/browse/DERBY-6854
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.12.1.1
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: d6854-classloader.diff, derby-6854-01-aa-fixFor9-ea.diff
>
>
> Early access versions of JDK 9 (build 100) have "9-ea" as the java.version
> and "9" as the java.specification.version. This confuses the
> JavaVersionHolder class which the regression tests use in order to determine
> the vm level. At a minimum, we need to make JavaVersionHolder recognize these
> early access strings.
> This issue can be left open even after a fix is applied because we have no
> idea how java.version and java.specification.version are going to evolve over
> the remaining development cycle for JDK 9.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
