Details
-
New Feature
-
Status: Closed
-
Must
-
Resolution: Fixed
-
None
-
None
-
Low
-
Platform 2.0 Alpha Sprint, Platform 2.0 Alpha Sprint 3, Platform 2.0 Beta Sprint 1
Description
The allergies API which we have in the module https://github.com/openmrs/openmrs-module-allergyapi needs to be moved into the core platform.
This requires moving java files, hibernate mapping files, liquibase changesets, from the module to core.
Classes in "org.openmrs.module.allergyapi" go to "org.openmrs"
Those in 'org.openmrs.module.allergyapi.api" go to "org.openmrs.api"
Then from "org.openmrs.module.allergyapi.api.db" to "org.openmrs.api.db"
From "org.openmrs.module.allergyapi.api.db.hibernate" to "org.openmrs.api.db.hibernate"
From "org.openmrs.module.allergyapi.api.impl" to "org.openmrs.api.impl"
Move classes in org.openmrs.module.allergyapi.resource to the REST Web Services module: https://github.com/openmrs/openmrs-module-webservices.rest
Changesets in liquibase.xml go to liquibase-update-to-latest.xml
The global properties in config.xml go to org.openmrs.util.OpenmrsConstants
Remember to also move the unit tests.
When done with the above, ensure that mvn clean install runs successfully and that you can run the web application and login.
After doing all the above, if the reference application was running on master, you would try run it without the allergies-api module and see if all is well.
Gliffy Diagrams
Attachments
Issue Links
- depends on
-
RA-617 Add service layer support to get Allergies by their UUID
-
- Closed
-
- is depended on by
-
RESTWS-557 Add Allergies REST API to webservices.rest
-
- Closed
-
-
RA-958 Allergy UI Module must build against OpenMRS 2.0 platform
-
- Approved
-
- is related to
-
TRUNK-4749 Remove the old problems lists implementation
-
- Closed
-
- relates to
-
TRUNK-4756 Migrate active lists to the new allergies tables
-
- Closed
-
- links to