Current state: Complete
1. Rename class packages to org.apache.knox.gateway
Modules should reflect appropriate subpackages as well. Let's determine a convention for package naming based on the grouping of client facing services in Knox.
We can discuss whether the subpackage conventions are really necessary.
- Proxying Services
- Authentication Services
- identity assertion
- Client Services
2. Provide Adapter classes for any classes that have likely been extended by consumer
Determining the specific classes that are currently being extended by our consumers is going to be a bit tricky.
There are a number of classes that are explicitly intended to be extended and I will try and list a few here.
Tests should help identify others.
We will need to provide adapter classes and should deprecate them from the start in order to facilitate a migration away from the old packages.