[
https://issues.apache.org/jira/browse/DERBY-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-2906:
-----------------------------------
Attachment: derby-2906-1a.diff
'/tmp/derby-2906-1a.diff' adds a delete action to the start of each jar build
target.
This ensures that nothing more than necessary is included in the jar file
(primarily from the META-INF directory), and it also requires the targets to
add everything that is needed themselves.
I compared the contents in the jars, and the only change I observed was the
exclusion of the META-INF/services directory from jars that shouldn't autoload
a Derby driver (only derby.jar and derbyclient.jar should).
Note that I added the delete action to all jar build targets.
I'm running suites.All. Unless I get pushback, I will commit tomorrow and then
merge the fix to the other branches in a week or so.
> derbynet.jar & derbytools.jar incorrectly have a
> META-INF/services/java.sql.Driver entry
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-2906
> URL: https://issues.apache.org/jira/browse/DERBY-2906
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.2.0, 10.3.0.0, 10.3.1.0, 10.4.0.0
> Reporter: Daniel John Debrunner
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-2906-1a.diff
>
>
> Only the jar files that contain the driver should have the autoloading
> services file for the JDBC driver.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
