[
https://issues.apache.org/jira/browse/DERBY-7058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963986#comment-16963986
]
Richard N. Hillegas commented on DERBY-7058:
--------------------------------------------
As Davide said, the embedded driver moved into the tools jar as part of the
JPMS modularization work done in Derby 10.15. This was our solution to the fact
that the org.apache.derby.jdbc package was split across the engine and client
jar files in earlier versions of Derby, violating the partitioning requirements
of JPMS. If you are interested in the discussion which resulted in this
decision, please see the commentary on DERBY-6945 beginning at
https://issues.apache.org/jira/browse/DERBY-6945?focusedCommentId=16302156&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16302156
> EmbeddedDriver is missing in maven-released derby jar
> -----------------------------------------------------
>
> Key: DERBY-7058
> URL: https://issues.apache.org/jira/browse/DERBY-7058
> Project: Derby
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 10.15.1.3
> Reporter: Eugene Chung
> Priority: Major
>
> org.apache.derby.jdbc.EmbeddedDriver is missing in
> [https://mvnrepository.com/artifact/org.apache.derby/derby/10.15.1.3]
> Or is EmbeddedDriver opted out? I can't find any announcement.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
