Hello,
I'd like to call your attention to this discussion:
https://issues.apache.org/jira/browse/DERBY-3083
The issue here is that the Derby Network Server looks for a JAR called
"derbynet.jar" on the classpath ... by *name*. Of course, when I use
Maven, the JAR is called "derbynet-10.3.1.4.jar" and the security
policy fails to find the file.
I'm by no means an expert to Java security policies but I thought I'd
let you know that there is something which might cause trouble. Is
anyone using Java security policies in Maven projects? Is there a
better way to handle "code domains" than specifying JAR file names?
Regards,
--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.pdark.de/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
