| Summary: | Test upgrading to a newer version of Spring security (2.0.7) | ||
|---|---|---|---|
| Product: | [Technology] Hudson | Reporter: | Duncan Mills <duncan.r.mills> |
| Component: | Core | Assignee: | Winston Prakash <winston.prakash> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Duncan Mills
I've started looking at Spring Security 2.0.7 which is compatible with Spring Source 2.5.6 The package name has changed, wondering how it would affect plugins if they used acegi AcegiSecurity 1.0.1 is replaced with Spring Security 2.0.7. This involved modification to about 70 classes. I have not tested every permutation combination. Need more testing around this later. http://git.eclipse.org/c/hudson/org.eclipse.hudson.core.git/commit/?id=f1a3880753e69e47fe7346dabf4833f3b3a7886c This modification brings in total of three libraries <dependency> <groupId>org.springframework.security</groupId> <artifactId>spring-security-core</artifactId> <version>2.0.7</version> </dependency> <dependency> <groupId>org.springframework.security</groupId> <artifactId>spring-security-acl</artifactId> <version>2.0.7</version> </dependency> <dependency> <groupId>org.springframework.ldap</groupId> <artifactId>spring-ldap</artifactId> <version>1.2.1</version> </dependency> |