[
https://issues.apache.org/jira/browse/UIMA-6365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho updated UIMA-6365:
---------------------------------------------
Fix Version/s: (was: 3.3.0uimaFIT)
> Warn or fail if a primitive field is marked as a non-mandatory parameter
> ------------------------------------------------------------------------
>
> Key: UIMA-6365
> URL: https://issues.apache.org/jira/browse/UIMA-6365
> Project: UIMA
> Issue Type: Improvement
> Components: uimaFIT-Maven-Plugin
> Reporter: Richard Eckart de Castilho
> Priority: Major
>
> The {{mandatory}} flag on configuration parameters indicates if the target
> field accepts a {{null}} value or not. For primitive fields, this is
> obviously not the case. Thus, for primitive fields, {{mandatory}} must always
> be {{true}} and if we want to avoid that the user actually has to specify the
> parameter every time, the {{defaultValue}} must be set. That makes the
> parameter effectively optional from the user's perspective.
> Probably the best place to catch this is the "generate" or "enhance" goal of
> the Maven plugin - which could immediately fail.
> It could also be detected by uimaFIT itself at runtime, but then it would be
> better just to warn (maybe warn less with high frequency).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
