[
https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540588
]
Daniel John Debrunner commented on DERBY-3083:
----------------------------------------------
Rather than checking the classpath (which is non-standard) and needs to be more
detailed(*) than derby.jar and derbynet.jar on the classpath, why not simply
see the name of the jar the network server code is coming from. The code must
already get the url to set up the properties for the server policy.
(*) Classpath could just be derbynet.jar, could be started using -jar command
with derbyrun.jar or derbynet.jar, ...
> Network server demands a file called "derbynet.jar" in classpath
> ----------------------------------------------------------------
>
> Key: DERBY-3083
> URL: https://issues.apache.org/jira/browse/DERBY-3083
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.3.1.4
> Reporter: Aaron Digulla
> Attachments: derby-716-10-datatypesCollation-aa.diff
>
>
> The network server will not start if the derbynet jar is added under a
> different name than "derbynet.jar" to the classpath. This makes it impossible
> to use it in maven projects where the jar is renamed to
> "derbynet-10.3.1.4.jar".
> This did work with 10.2.2.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
