db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3083) Network server demands a file called "derbynet.jar" in classpath
Date Wed, 10 Oct 2007 14:49:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533750

Rick Hillegas commented on DERBY-3083:

On derby-dev, Bryan suggests another solution:

Alternatively, perhaps we could have a glance at the classpath
during startup, perhaps by sharing the code that sysinfo uses,
and only install the default policy if the user appears to
be using the default set of jars.

That is, if we don't see derby.jar, derbynet.jar on the
classpath when starting up Network Server, then we assume that
the user has taken control of the *entire* configuration process,
including the configuration of the security policy, and so we
don't attempt to install a default security policy in that case. 

> 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:
>            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-".
> This did work with

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message