SEC-1132: Package refactoring to reflect new modules #1381

Closed
spring-issuemaster opened this Issue Mar 26, 2009 · 2 comments

1 participant

@spring-issuemaster

Luke Taylor (Migrated from SEC-1132) said:

Non-core modules should come under specific sub-packages, e.g. org.springframework.security.ldap, rather than creating subpackages within the core

@spring-issuemaster

Luke Taylor said:

After discussion with Ben, we also think that the core packages should be restructured to reduce inter-package dependencies and also to cut down the number of packages immediately below org.sf.security. This would also be more osgi friendly.

Suggestions are

org.sf.security.access – access control/authorization functionality
org.sf.security.authentication – authentication-specific packages

@spring-issuemaster

Luke Taylor said:

Mostly done. After some detailed package analysis most of the codebase packages have been restructured to make the code more modular and reduce circular dependencies.

@spring-issuemaster spring-issuemaster added this to the 3.0.0 M1 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment