db-derby-dev mailing list archives

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

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

Aaron Digulla commented on DERBY-3083:

Does any documentation indicate that it's *not* ok to change the JAR name? :-) This is Java
after all and I'm used that I can use what I can put on the classpath. Moreover, when you
use Maven, then the JAR names must include the version number. So this change makes it impossible
to use Derby with Maven.

I'm using Derby extensively to replace a real DB2 for my test cases and I couldn't care less
about a security policy. It's nice to have one shipped with the product but I fail to see
the advantage to make it the *default*.

> 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