[
https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529492
]
Kathey Marsden commented on DERBY-3083:
---------------------------------------
Aaron said:
>In that case, the security manager should be fixed not to rely on a fix jar
>name :-) What happens when I >patch the JAR or feed Java a completely
>different JAR as "derbynet.jar"?
I agree. perhaps Rick has some ideas on how to achieve this since he
implemented the functionality For the sake of backward compatibility I think
at least the start should not fail and perhaps just print a warning to
derby.log that the security manager was not installed.
> 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
>
> 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.
