Hi Kiran, Thanks for taking care of this!
Looks like we could re-organize the project much better if we get the naming issue resolved first. For example, if Kerby is used, maybe ‘kerby-asn1’ would be a choice, which allows it to be used in other contexts/projects without worrying about polluting their global namespace. Just a quick reply. Will provide my thoughts for each item thoroughly late today. Regards, Kai From: Kiran Ayyagari [mailto:[email protected]] Sent: Wednesday, January 14, 2015 8:11 AM To: Apache Directory Developers List Subject: [Kerberos] re-organizing the module structure I suggest we reorganize the modules under directory-kerberos. All the modules under 'contrib' are essential components hence must be moved to the project root directory. Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms like 'pkix', 'token' etc there. Move 'haox-kdc/kdc-server' to the root level and the create a new folder at the root level to hold all the backend implementations (and the ldap-identity-backend will be moved here). 'contrib' folder can be used to store any contribution from other parties. And, we should drop the project prefix from the folder names and set that prefix in <artifactId> in the respective module's pom.xml. For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml to contain <artifactId>haox-asn1</artifactId> wdyt? -- Kiran Ayyagari http://keydap.com
