Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0
-
Fix Version/s: 1.0
-
Component/s: Configuration, Development, Documentation
-
Labels:None
Description
There are a couple of issues here:
1. Why is a sample version of rice-config.xml not included in the non-sample app distribution of the standalone server? I cannot think of a good reason to exclude it.
2. Among the currently included parameters, which are specific to KFS/IU and which are kruft?
Plan is to take the wsa131 copy of the file, put it in the web module, and use maven to filter it on a per-profile basis such that the standalone gets a generic version, the sample app gets a sample-app version and the wsa131 profile creates a flavor for the IU environment.
Attachments
Issue Links
- is related to
-
KULRICE-2934 Verify that Rice Config is as streamlined as possible and that the usage of common-config-defaults.xml is working properly
-
- Closed
-
- relates to
-
-
- Resolved
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | wsa131-rice-config.xml [ 33512 ] |
| Attachment | wsa131-ci_rice-config.xml [ 33615 ] |
| Attachment | wsa131-kr-stg_rice-config.xml [ 33616 ] |
| Attachment | common-config-defaults.xml [ 33617 ] |
| Link |
This issue is related to |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Comment | [ the common-config-defaults file David refers to; located in <project base dir>/imp/src/main/resources/META-INF/common-config-defaults.xml ] |
| Comment | [ rice-config.xml used by test server deployed to kuali6 on wsa131 ] |
| Comment | [ rice-config.xml used for 0.9.4 continuum build on wsa131 ] |
| Link |
This issue relates to |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Workflow | custom [ 65501 ] | Copy of custom for rice [ 210838 ] |
| Workflow | Copy of custom for rice [ 210838 ] | custom [ 220586 ] |
| Workflow | custom [ 220586 ] | Rice Workflow [ 230334 ] |