Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: 1.1.2
-
Fix Version/s: 1.3.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- All
Activity
| Field | Original Value | New Value |
|---|---|---|
| Resolution | Won't Fix [ 2 ] | |
| Status | New [ 10000 ] | Resolved [ 10004 ] |
| Priority | Minor [ 4 ] |
| Status | Resolved [ 10004 ] | Closed [ 10005 ] |
| Fix Version/s | 1.3.0 [ 10346 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|

The SU configuration should never be accessed directly.
If people want to add new parameters, they should add a properties file in the SU.
Additional resources can be used by using the class loader.
Here is an example.
As this use case is not very common, there is no interest in adding an API method for it, in particular when there is a workaround.