[
https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540712
]
Aaron Digulla commented on DERBY-3083:
--------------------------------------
Rick: This again breaks the idea of "least surprise". The network server should
not try to install a security manager at all until told so. The first breaking
of that rule is what caused the problems in the first place.
I suggest that you remove the code which tries to install the SM by default and
add new code which is enabled by an option (property or command line). That
option should either be "yes/no" if you can figure out the name of the JAR or
it should specify the name of the JAR which contains the preferred SM. If the
option is given and no SM can be installed, an exception should be thrown,
aborting the program.
This would give control to the user instead of involving further black magic
which will only lead to a long series of bugs and patches, all because of
breaking "least surprise" again and again.
> 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.
