Now I looked at the patch for DERBY-668, and I don't see that it addresses DERBY-622 at all...
I think my little patch - although not any great shakes, is still for the intended bug an improvement in that you see at least the info of the .properties files of the .jar file in which it sits...without granting any additional accesses in the (derby_tests).policy file.
It doesn't totally address the 622 bug because the test will still fail if you take out the // .... 622 lines in the derby_tests.policy file (so my patch doesn't do that).
I don't think the two patches really interfere, although I can imagine an automated merge to get confused...So whomever gets to take the merge needs to be careful...
Or you can pick this bug up and figure out what I did wrong. :-)
I had one tiny question prompted your changes for DERBY-668 - you modified the method tryAsResource - I didn't bother with it because eclipse thought it wasn't used and it's not a public method...Should I have changed it?
Myrna
On 3/9/06, Myrna van Lunteren <[EMAIL PROTECTED]> wrote:
Hi Bryan,I admit I didn't look at your patch for DERBY-668, as I was under the impression you were looking into the permissions for properties...I'll try to have a look at your patch...However, note that I did not assign the issue to myself, because there are some other matters I want to focus on...:-)Myrna
On 3/9/06, Bryan Pendleton <[EMAIL PROTECTED] > wrote:Myrna van Lunteren (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-622?page=comments#action_12369771 ]
Myrna, I think that you and I have been working on a closely
related problem. You might want to have a close look at the various
comments in DERBY-668, because we've been discussing a number of
sysinfo permissions problems in the comments on that JIRA issue.
Probably you and I should compare notes so that I don't accidentally
interfere with the work you're doing on this issue (I confess that
I wasn't paying enough attention to DERBY-622 until recently).
In the meantime, I'll have a closer look at your work on DERBY-622 and
consider how it interacts with my DERBY-668 efforts.
thanks,
bryan
