To simplify distribution and to avoid duplication between client and server, the code for each subsystem should be grouped into 3 separate jar files: - common (e.g. KeyRequestResource) - server (e.g. KeyRequestResourceService) - client (e.g. DRMRestClient)
The client will use the common and client jar files, for example: - pki-kra.jar - pki-kra-client.jar
The server will use the common and server jar files, for example: - pki-kra.jar - pki-kra-server.jar
To simplify the packaging process, the code could be reorganized into packages that match the distribution, for example: - common: com.netscape.pki.kra - server: com.netscape.pki.kra.server - client: com.netscape.pki.kra.client
Each jar file may contain many other subpackages, for example the server jar file may contain the following subpackages: - com.netscape.pki.kra.server.dbs - com.netscape.pki.kra.server.jobs - com.netscape.pki.kra.server.servlet
Design document is available at http://pki.fedoraproject.org/wiki/Packaging.
This is a code refactoring which doesn't affect the user.
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: UNTRIAGED
This is a continuous improvement. No need to keep track.
Metadata Update from @edewata: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None (was: Future) - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/686
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.