Community
Participate
Working Groups
AccessRuleSet.getViolatedRestriction compares rules against paths using '/' as a path seperator. The access rule patterns being passed in use '/'. However, the target file path being matched against may use '\' as the seperator if it is coming out of a directory as opposed to a jar (see FileSystem.findClass). With recent support from pde.build to support passing access rules, releng builds will be getting many invalid warnings because of this.
Created attachment 31145 [details] patch This is the patch I've been using to fix this problem in my local workspace. Is this something we can get fixed for tomorrow's integration build? Jeff is going to ApacheCon next week and we would like to be able to demo our support for access rules.
Fixed and released in HEAD. Modified AccessRuleSet.getViolatedRestriction to accept '\' in targetTypeFilePath when running on Windows.
Verified for 3.2 M4 using build I20051212-0010