[
https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3083:
---------------------------------
Attachment: derby-3083-01-requireDerbynet-ab.diff
Thanks for the quick feedback, Dan. Attaching
derby-3086-01-requireDerbynet-ab.diff. You are right that endsWith()
accomplishes what I want much more clearly. I have also expanded the comment on
packagingLooksGood().
I am not tackling the Maven versioning scheme here. Someone else is welcome to
take that on. I am tackling what I see to be the regression introduced by
DERBY-2196:
1) The server crashes immediately if it can't find a jar file named
derbynet.jar.
With this patch, the server will boot against the Mavenized jars--but it won't
install a security manager.
I think there is a follow-on enhancement which someone else is welcome to log
and tackle:
2) Make the server install a SecurityManager if the derby jars have names which
conform to some other naming convention.
> 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-3083-01-requireDerbynet-aa.diff,
> derby-3083-01-requireDerbynet-ab.diff, 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.
